IOException: Unable to read resource content

rsclmumbai

CentOS Linux release 8.0.1905 (Core)
PHP 7.2.26

Last night I migrated from 1.12-git to v1.15.1.
I installed the plugin to save attachments to file system & migrated existing attachments from DB to FS

Everything is working well but I have received 2 system notification emails with the above subject line:

Sub: IOException: Unable to read resource content
Msg: /tmp/php0yvJAA: Unable to move file

How do I fix this?

Thanks

rsclmumbai

One more...

(root)/OSTAttachments/p/psA_mN8pUwqGVQWSs9Fo_Z2OKICJVB-A: Unable to delete file

#0 (root)/include/class.file.php(147): FilesystemStorage->unlink()
#1 (root)/include/class.file.php(671): AttachmentFile->delete()
#2 (root)/include/class.thread.php(629): AttachmentFile::deleteOrphans()
#3 (root)/include/class.thread.php(749): Thread->deleteAttachments()
#4 (root)/include/class.ticket.php(3618): Thread->delete()
#5 (root)/include/class.ticket.php(1491): Ticket->delete()
#6 (root)/include/ajax.tickets.php(1396): Ticket->setStatus()
#7 (root)/include/class.dispatcher.php(145): TicketsAjaxAPI->setTicketStatus()
#8 (root)/include/class.dispatcher.php(38): UrlMatcher->dispatch()
#9 (root)/include/class.dispatcher.php(120): Dispatcher->resolve()
#10 (root)/include/class.dispatcher.php(38): UrlMatcher->dispatch()
#11 (root)/scp/ajax.php(316): Dispatcher->resolve()
#12 {main}

rsclmumbai

Just to update:

OSTAttchment folder (where attachments are stored) is in OSTicket Root folder.

Permissions of "OSTAttchment" is 777 recursively (I'm aware its unsafe)
drwxrwxrwx 66 root root 4096 Jan 5 19:42 OSTAttachments
SELinux = disabled

What else should I be looking at -- any pointers?
Thanks

ntozier

mod_security?

What user does the webserver run as?

rsclmumbai

ntozier "root"

I don't believe its a mod_security issue. If it was, I would get errors all the time. I get the foresaid error randomly.

What else should I look for?

ntozier

Honestly I can't think of anything else atm. AV software?

I'll ask the devs to take a look at this thread maybe they will have an insight I dont have.

KevinTheJedi

@rsclmumbai

Unable to read source content means the system was unable to read the file contents to display in the system. Typically this means permissions/ownership issues.

Unable to move file typically means permissions/ownership issues where the system was unable to move the file contents from the tmp directory to the storage backend.

Unable to delete file typically means permissions/ownership issues where the system couldn’t delete the file. It could also mean the file doesn’t actually exist on the file system.

Cheers.

rsclmumbai

One thing that has come to my mind is that when I installed the plugin and created the folder for attachments, I set the permissions as
chmod -R 777 OSTAttachments/

Over time, OSTicket created folders within 'OSTAttachments/'

Seems like, the write permission does not / did not traverse to the new sub-folder inside 'OSTAttachments/'

Today I executed the same chmod command again.
Its been 12 hours & I have not received any notifications about "IOException: Unable to read resource content"

I may be totally off here, sharing my hypothesis nevertheless

Thanks!

ntozier

That's a good hypothesis. 🙂 Thanks for sharing it. I will make sure that @KevinTheJedi sees this.

rsclmumbai

Thanks!!

jrawbits

I looked into this thread having a similar problem (Cannot read resource) and discovered another thing that can lead to that specific error: running the api/cron.php file with the wrong user will generate an IOException about not reading the resource. It appears to work if the cron job runs as the same user as the web server (but the key is probably to make sure that any file written by that user can be read by the web server).