Following install of ITSM packages on RPM version of current release, Centos 6 x86_64:
Forwarding for documentation purposes. > One additional change was needed: > > # cd /opt/otrs > # bin/otrs.SetPermissions.pl --otrs-user=otrs --otrs-group=apache --web- > user=apache --web-group=apache /opt/otrs > > Also, their startup script is a little squirrely, and talks about the PID > being > registered in the "database". That may be, but they also have a PID file in > /opt/otrs/var/run/ that needs to be maintained. > > Running > > /opt/otrs/bin/otrs.Scheduler.pl -a stop --force > > then manually using "ps" to verify it's really dead, seems to be a reliable > way > of getting it to reset itself completely. If you run "service > otrs-scheduler-linux > start" and get anything other than "Starting OTRS Scheduler [OK]" as a result, > then it was *not* properly reset first. > > This was working fine until I did the installation of ITSM module. I think > their > package manager tried and failed to restart the scheduler and didn't recover > gracefully afterward. --------------------------------------------------------------------- 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
