Thanks to Carl and Víctor for the help. I was out of town for the weekend and didn't get a chance to check the system until this morning. It turns out to be a pretty silly mistake and possibly no one else would make the same mistake. In short, I usually switch to root when I need to run "make install". In this case, I did that and then batch changed some of the files to user "base" and group "base". Thus "jobrunner" has totally wrong settings. Once I reinstalled the BASE in the correct way, everything works. Really sorry for the mess. By the way, Carl, could you explain a little bit more about how the memory usage is controlled in plugins? I have read your note on 2005-03-02, but didn't quite get it. In my case, I have only one machine, with 6G memory. In PHP, I set the memory limit to 1.5G. However, in BASE, for example, for the plugin "pinbased_lowess", I can only set 128M memory to it. Whenever I increase the number, I got the error message same as Etienne got "Aborted by jobManager: No computation servers are capable of running this job. Limiting factor(s): RAM". How can I solve this problem? Thanks in advance. Thanks again and wish you all a good day. Zhilin
________________________________ From: [EMAIL PROTECTED] on behalf of Carl Troein Sent: Fri 2/17/2006 3:04 AM To: basedb-users@lists.sourceforge.net Subject: Re: [base] Help needed on jobRunner Víctor Real wrote: > try to edit manually /etc/passwd to change uid grom 502 to 503 > > At 06:57 p.m. 16/02/2006, you wrote: >> Hi, Friends, >> >> We have recently installed Base 1.2.17 with the configuration of >> "--with-jobrunner-user=basejob --with-jobrunner-group=base ". >> >> But now when we try to run any plugins, we got the error message like >> this: >> "jobRunner: the effective (suid) UID must be 503 (current euid: 502) >> *** Program returned 125" Manually changing a UID could (and probably will) have all sorts of bad consequences. Files would suddenly belong to the wrong user, and if someone has UID 503 now, that person will probably not be happy either. Zhilin, when you did the 'make install' the correct owner and flags (the suid bit) should've been set for bin/jobRunner. What does an "ls -l bin/jobRunner" show? Here I get this: -r-sr-s--- 1 basejob base 9051 Nov 29 21:20 bin/jobRunner and as you see both the user and the 's' bits are correct. If the file permissions are wrong, it might have something to do with happened at 'make install' time. And it they are correct, it could maybe be that your file system is mounted with the nosuid flag? If you don't mistrust the plugins you're going to run (and by mistrust I mostly mean that you're not 100% sure that they won't accidentally remove files that they shouldn't touch), you're probably better off without the --with-jobrunner-* flags, since it complicates the installation a bit to use them. //Carl -- Carl Troein - [EMAIL PROTECTED] http://www.thep.lu.se/~carl/ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642 _______________________________________________ The BASE general discussion mailing list basedb-users@lists.sourceforge.net unsubscribe: send a mail with subject "unsubscribe" to [EMAIL PROTECTED]
<<winmail.dat>>
