We have been running Baan IV c4 on a linux server since over half a year now.
Our jobs are starting by crontab (root).
Until yesterday all was ok, but now the jobs are not running anymore. Cron start the jobs (with rc.startjob) in the normal way, as I can see in the log files, which are containing no errors. But the jobs are not starting in baan.
In logfile rc.startjoberr all looks ok:

Connecting with bshell...
Connection established.

All log files on the OS are written as normal. I could not found any error in the baan log files. I also tried to start the job by an "normal" superuser, not root - same.

Hopefully someone have a hint for me

Alex Preyer

Correction: I tried again another superuser for starting a job and there it works! But why not with root?

Is root using the correct package combination?
Review the settings of the Baan user that does work against the settings of Baan user root (including unix env. variables).

If things suddenly stop working, the challenge is to find out what changed.
In your case, if things work correctly when run under a superuser account, then the root account settings are definitely suspect.

Second rule of thumb, don't use the root account ;)

Thanks for the replies.
Yes I checked all like Package and so on. Bthw. there were no changes before the problem occured.
But you´re right, since running the jobs by another user all has been running well now. But nevertheless I ask myself why this issue appeared over night without any system changes.

Thanks
Alex

Hi there,

have a look at $BSE/lib/user .....
here you find the actual params fur users (for instance uroot) as well as the last version (uroot-) ...
what are the timestamps of these files?
Just an idea .... someone changed the PC of user root, but nevver did a conversion to runtime (some time ago).
Now recently someone changed any setting of probably another user and converted to runtime, thus applying the (old) changes for user root.
But if something like this happened, the timestamps should prove so.

regards

Norbert