
Alan,
Actually, I don't understand where the error message you get, "Message:
Can't remove shm for log: Operation not permitted" comes from. I understand
that OTRS tries to do a Kernel::System::Log Cleanup () but why it can't do
that, beats me.
If there is anyone other who'd like to help you with this, that would be
great.
Regards,
--
Michiel Beijen
Software Consultant
+31 6 - 457 42 418
Bee Free IT + http://beefreeit.nl
On Thu, Jul 30, 2009 at 12:17, Alan McKay
Any further comment on the below? Or am I going to have to back out of my upgrade?
On Wed, Jul 29, 2009 at 12:53 PM, Alan McKay
wrote: Did you put the new files of 2.4.2 in the 2.3.4 directory?
Yes, that's what you told me to do, no? What I actually did was create another symlink from /opt/otrs-2.4.2 to /opt/otrs-2.3.4, because the tarball has the directory name "otrs-2.4.2" built into it. So I copied the tarball to /opt, cd'd to there, made the symlink, then untarred the tarball. Since the symlink was in place, all the files went into 2.3.4 directory (I verified this)
- Are you the otrs user?
Yes, which is what I am supposed to be, right?
It seems you don't have permission on the shared memory used for the log file.
Where is that?
-- “Don't eat anything you've ever seen advertised on TV” - Michael Pollan, author of "In Defense of Food"
-- “Don't eat anything you've ever seen advertised on TV” - Michael Pollan, author of "In Defense of Food" --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/