okay, after modifying crontab, I now get the following error message: Use of uninitialized value in concatenation <.> or string at /opt/OpenTRS/bin/UnlockTickets.pl line 25. Can't locate Kernel/Config.pm in @INC <@INC contains: /../
Hi Jon, On Wed, Nov 20, 2002 at 04:52:44PM -0600, Jon Conkle wrote:
okay, after modifying crontab, I now get the following error message: Use of uninitialized value in concatenation <.> or string at /opt/OpenTRS/bin/UnlockTickets.pl line 25. Can't locate Kernel/Config.pm in @INC <@INC contains: /../
In $OTRS_HOME/var/cron/* are all cron jobs for the otrs user located. Its better to do the changes there, because on the next otrs-cron-reload (bin/Cron.sh start) your changes of (crontab -e otrs...) are lost. I think your problem is maybe the wrong $HOME of the otrs use. The easiest way to check this is "su - otrs" and then "$OTRS/bin/Cron.sh restart". If you get still an error message would a bug entry in http://bugs.otrs.org/ fine! Thanks, Martin -- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ -- Perfection is our goal, excellence will be tolerated. -- J. Yahl
On Thursday, November 21, 2002, at 01:30 AM, Martin Edenhofer wrote:
In $OTRS_HOME/var/cron/* are all cron jobs for the otrs user located.
Its better to do the changes there, because on the next otrs-cron-reload (bin/Cron.sh start) your changes of (crontab -e otrs...) are lost.
Aren't the files there overwritten when someone upgrades? :) I can't find anything that references otrs-cron-reload in the distribution, is that new in CVS? I didn't use the bin/Cron.sh script because it's hardcoded to use #!/bin/bash, which doesn't exist on my system. And the arguments to crontab are different on my system (you have 'crontab $CRON_USER $CRON_TMP_FILE' - with the crontab command in FreeBSD (all BSDs?) this would need to be 'crontab -u $CRON_USER $CRON_TMP_FILE', unless you're running it as the otrs user in which case it's just 'crontab $CRON_TMP_FILE'). BTW, I notice bin/Cron.sh uses /tmp for it's temporary file instead of $HOME/var/tmp - why is that? Bryan
Hi Bryan, On Thu, Nov 21, 2002 at 07:59:21AM -0500, Bryan Fullerton wrote:
In $OTRS_HOME/var/cron/* are all cron jobs for the otrs user located.
Its better to do the changes there, because on the next otrs-cron-reload (bin/Cron.sh start) your changes of (crontab -e otrs...) are lost.
Aren't the files there overwritten when someone upgrades? :)
Ok! ,-) I move this files ($OTRS_HOME/var/cron/*) to $OTRS_HOME/var/cron/*.dist. -=> The same as Kernel/Config.pm.dist! Copy to Kernel/Config.pm on setup. I add this info to the changes file...
I can't find anything that references otrs-cron-reload in the distribution, is that new in CVS?
There is a new point (since 0.5 Beta8) in INSTALL. [...] 10. Cronjobs for the OTRS user: --------------------------- There are several OTRS cronjobs in $OTRS_HOME/var/cron/*. Use $OTRS_HOME/bin/Cron.sh {start|stop|restart} to start or stop this cronjobs. >> Note: Install this cronjobs as OTRS user. << [...]
I didn't use the bin/Cron.sh script because it's hardcoded to use #!/bin/bash, which doesn't exist on my system. And the arguments to
Ja! ;-/ I changed it on 3 weeks ago (http://lists.otrs.org/pipermail/otrs/2002-October/000341.html).
crontab are different on my system (you have 'crontab $CRON_USER $CRON_TMP_FILE' - with the crontab command in FreeBSD (all BSDs?) this would need to be 'crontab -u $CRON_USER $CRON_TMP_FILE', unless you're running it as the otrs user in which case it's just 'crontab $CRON_TMP_FILE').
I think it's the same (also on BSD). "crontab -u $CRON_USER $CRON_TMP_FILE" if root use it and "crontab $CRON_TMP_FILE" if the normal user use it. $CRON_USER is empty in bin/Cron.sh.
BTW, I notice bin/Cron.sh uses /tmp for it's temporary file instead of $HOME/var/tmp - why is that?
Thanks! I changed it.
Bryan
Martin -- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ -- "The number of Unix installations has grown to 10, with more expected." The Unix Programmer's Manual, 2nd Edition, June 1972
Okay, i created user otrs before i installed OTRS. However, for some reason a home directory was never created for that user (i never noticed until now). So i assume that when OTRS is installing, it's supposed to copy a bunch of stuff into that home directory? that's the problem? if so, do i need to manually create a home directory for otrs user and then reinstall OTRS, or can i fix this without reinstalling? Martin Edenhofer wrote:
In $OTRS_HOME/var/cron/* are all cron jobs for the otrs user located.
Its better to do the changes there, because on the next otrs-cron-reload (bin/Cron.sh start) your changes of (crontab -e otrs...) are lost.
I think your problem is maybe the wrong $HOME of the otrs use.
The easiest way to check this is "su - otrs" and then "$OTRS/bin/Cron.sh restart".
Hi Jon, On Thu, Nov 21, 2002 at 10:14:27AM -0600, Jon Conkle wrote:
Okay, i created user otrs before i installed OTRS. However, for some reason a home directory was never created for that user (i never noticed until now). So i assume that when OTRS is installing, it's supposed to copy a bunch of stuff into that home directory? that's the problem? if so, do i need to manually create a home directory for otrs user and then reinstall OTRS, or can i fix this without reinstalling?
You don't need to reinstall it. Just check the $HOME of the otrs user. It should be the OTRS-root-directory. So if you installed OTRS in /opt/OpenTRS (just an example) the $HOME of the otrs user should be /opt/OpenTRS. If it is /home/otrs, change the home of the otrs user in /etc/passwd [...] otrs:x:UserID:GroupID:OTRS User:/home/otrs/:/bin/true [...] to: [...] otrs:x:UserID:GroupID:OTRS User:/opt/OpenTRS/:/bin/true [...] And bin/Cron.sh should work fine. Martin -- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ -- "Security is a process, not a product." - Bruce Schneider
participants (3)
-
Bryan Fullerton -
Jon Conkle -
Martin Edenhofer