BeeOND - pid file and log

419 views
Skip to first unread message

Michal Pitonak

unread,
Jul 31, 2018, 8:39:24 AM7/31/18
to beegfs-user
Hi all,

could you please give me a hint on how to change the default location of the pid file (default: /var/run) and the log file (default: /var/log) ?

If I got the BeeOND idea right, the "beeond start ..." command should be run by user, which typically doesn't have r/w permissions to the aforementioned locations. I couldn't find any cli option or config file entry related to this issue...

Thank you very much,
Michal

Toby Darling

unread,
May 31, 2019, 12:00:22 PM5/31/19
to fhgfs...@googlegroups.com
Hi All

On 31/07/2018 13:39, Michal Pitonak wrote:
> Hi all,
>
> could you please give me a hint on how to change the default location
> of the pid file (default: /var/run) and the log file (default:
> /var/log) ?

I've been looking at beeond this week, and notice that the 'start'
options in 7.1.3 has

-L PATH => Log file directory. If necessary, the directory will be
created. Default: /var/log

That works great, but Michal's point about /var/run is still an issue.

toby@m02[beeond]: beeond start -n ~toby/projects/beeond/nodes -d /ssd -c
/beeond -p 5000 -f /gridware/sge/lmb/beeond -P -L /tmp/beeond
INFO: Using status information file: /var/tmp/beeond.tmp
...
INFO: Starting beegfs-mgmtd processes
INFO: Management daemon log: /tmp/beeond/beegfs-mgmtd_20190531-150049.log
INFO: Starting beegfs-mgmtd on host: host146
Unable to lock working directory lock file:
/var/run/beegfs-mgmtd-20190531-150049.pid; SysErr: Permission denied

Error: Unable to create/lock PID file:
/var/run/beegfs-mgmtd-20190531-150049.pid

[BeeGFS Management Node Version: 7.1.3
Refer to the default config file (/etc/beegfs/beegfs-mgmtd.conf)
or visit http://www.beegfs.com to find out about configuration options.]

ERROR: Unable to start beegfs-mgmtd on host: host146


Has anyone solved this?

Cheers
Toby

Sun Panny

unread,
Jun 2, 2019, 8:13:36 PM6/2/19
to fhgfs...@googlegroups.com
Hi,

Would you please try to use root user to try one more time.

I remember I have the same problem like you, you can try with root.

Thanks.
> --
> You received this message because you are subscribed to the Google Groups "beegfs-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to fhgfs-user+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/fhgfs-user/879c8a2e-dc80-b0eb-b132-2f921bdcfd77%40mrc-lmb.cam.ac.uk.
> For more options, visit https://groups.google.com/d/optout.

nwe...@g.harvard.edu

unread,
Jun 3, 2019, 2:23:12 AM6/3/19
to beegfs-user
The pidfile location could be worked around by hacking the beeond shell script, but the "modprobe" and "mount" commands called in that shell script would still be problematic for an unprivileged user.

-- 
Nathan 

Toby Darling

unread,
Jun 3, 2019, 5:53:26 AM6/3/19
to fhgfs...@googlegroups.com
Hi Sun

Thanks for your reply. Yes, it works fine when run as root, but I'd like
my users to be able to use beeond without needing sudo/root

Cheers
Toby
Cheers
Toby
--
Toby Darling, Scientific Computing (2N249)
MRC Laboratory of Molecular Biology
Francis Crick Avenue
Cambridge Biomedical Campus
Cambridge CB2 0QH
Phone 01223 267070
Reply all
Reply to author
Forward
0 new messages