Hi, I found a solution. The problem was the /var/log wasn´t accessible for the slurm-user. After fixing this and manually compiling the log-files stated in"slurmctld -cDvvvvv", the daemon is running. :-) Maria
2015-01-08 7:31 GMT+01:00 Maria Kreutel <[email protected]>: > Hi, > Chris you`re right, I used apt-get for munge and slurm-llnl > cat /etc/issue: Debian GNU/Linux 7 \n \l > Maria > > > 2015-01-08 0:04 GMT+01:00 Christopher Samuel <[email protected]>: > >> >> On 08/01/15 08:50, Maria Kreutel wrote: >> >> > I´m trying to set up slurm for a cluster which consists of Head- and >> > Compute node (Debian 4.6.3-14). >> >> What does cat /etc/issue say? >> >> There was no Debian 4.6.3, Debian 4.0 was codename Etch and released in >> 2007 and that went up to 4.0r9 as the last release in 2010 before being >> archived. 4.6.3-14 *looks* like the GCC version number in Debian Wheezy >> (v7). >> >> > I installed munge (munge-0.5.10) via rpm and got it running on both head >> > and node. I installed slurm-llnl (2.3.4-2) via rpm as well >> >> If this is Debian you shouldn't be installing with RPM, you should be >> installing with apt-get (or aptitude) instead. >> >> In current Debian releases the Slurm packages are called slurm-llnl, but >> in the next major release (Jessie, aka 8.0) it will become slurm-wlm >> (with slurm-llnl being a transitional "dummy" package to facilitate the >> rename on systems being upgraded). >> >> You can see more information here: >> >> https://tracker.debian.org/pkg/slurm-llnl >> >> If you're on Wheezy that will give you Slurm 2.3.4 (Jessie will have >> Slurm 14.03.9). >> >> Hope this helps! >> 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 >> > >
