Hello Lachlan, Thank you for your reply.
Yes, you're right. munge.socket.2 is created when the system runs..huhu I use Slurm version 15.08.10. The OS is Ubuntu 14.04 LTS 64 bit. Currently, I have installed munge and slurm successfully. Previously, munge.socket.2 unable to be accessed because at configure time I used a customized location in "--prefix=" option. So I decided to reinstall munge using the instructions available in this link https://github.com/dun/munge/wiki/Installation-Guide. Regards, Husen On Fri, Apr 8, 2016 at 9:00 AM, Simpson Lachlan < [email protected]> wrote: > Husen, > > > > You won’t be able to find the file – it’s created when the system runs so > that the system knows something is running J > > > > Everything in /var/run is ephemeral. > > > > Ok, what version of slurm are you running, which bits have you installed > and what OS are you installing it onto? > > > > Yes, there isn’t a munge in /var/run yet – that’s why you should create > the tmpfiles.d like I said – that will create it on boot. In the meantime, > you can just create the directory in /var/run/, you will need to chown > munge:munge after you have created it. > > > > Cheers > > L. > > > > *From:* Husen R [mailto:[email protected]] > *Sent:* Thursday, 7 April 2016 12:07 PM > *To:* slurm-dev > *Subject:* [slurm-dev] Re: Failed to access munge.socket.2 > > > > Hello Lachlan,Chris > > > > Thank you for your reply. > > > > I don't know why "/usr/local" is appended to the path.. > > I tried to locate munge.socket.2 manually using locate command and the > file is not exist indeed. > > The directory /usr/local/var/run/munge is empty. > > > > There is no munge directory in /var/run. I don't know why the munge > directory is located in /usr/local/var/run instead of in /var/run. > > > > I have ever installed slurm-llnl from repository before installing it from > source. is this probably the cause of the problem ? > > > > Regards, > > > > Husen > > > > On Thu, Apr 7, 2016 at 8:26 AM, Christopher Samuel <[email protected]> > wrote: > > > On 06/04/16 19:50, Husen R wrote: > > > however, when I tried to run sbatch I get the following error message: > > > > Failed to access "/usr/local/var/run/munge/munge.socket.2": No such file > > or directory > > Is that path really correct? > > On our systems it's: /var/run/munge/munge.socket.2 > > Best of luck, > Chris > -- > Christopher Samuel Senior Systems Administrator > VLSCI - Victorian Life Sciences Computation Initiative > Email: [email protected] Phone: +61 (0)3 903 55545 > http://www.vlsci.org.au/ http://twitter.com/vlsci > > > This email (including any attachments or links) may contain confidential > and/or legally privileged information and is intended only to be read or > used by the addressee. If you are not the intended addressee, any use, > distribution, disclosure or copying of this email is strictly prohibited. > Confidentiality and legal privilege attached to this email (including any > attachments) are not waived or lost by reason of its mistaken delivery to > you. If you have received this email in error, please delete it and notify > us immediately by telephone or email. Peter MacCallum Cancer Centre > provides no guarantee that this transmission is free of virus or that it > has not been intercepted or altered and will not be liable for any delay in > its receipt.
