I also run both commands using sudo so I am assuming permission should not be the issue ? my cluster user is root (i know not good, but im testing things out)
On Fri, May 31, 2024 at 12:03 AM Radhouane Aniba <arad...@gmail.com> wrote: > Yes when I run it manually it says something like this > > [2024-05-31T00:20:01.142] Accounting storage MYSQL plugin loaded > [2024-05-31T00:20:01.146] slurmdbd version 19.05.5 started > > But when I try to do it through systemctl > > [2024-05-31T00:21:30.953] Terminate signal (SIGINT or SIGTERM) received > [2024-05-31T00:21:30.953] debug: rpc_mgr shutting down > > > > On Fri, May 31, 2024 at 12:01 AM Ryan Novosielski <novos...@rutgers.edu> > wrote: > >> Are you looking at the log/what appears on the screen, and do you know >> for a fact that it is all the way up (should say "version <whatever> >> started” at the end)? >> >> If that’s not it, you could have a permissions thing or something. >> >> I do not expect you’d need to extend the timeout for a normal run. I >> suspect it is doing something. >> >> -- >> #BlackLivesMatter >> ____ >> || \\UTGERS, >> |---------------------------*O*--------------------------- >> ||_// the State | Ryan Novosielski - novos...@rutgers.edu >> || \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ >> RBHS Campus >> || \\ of NJ | Office of Advanced Research Computing - MSB >> A555B, Newark >> `' >> >> On May 30, 2024, at 23:57, Radhouane Aniba <arad...@gmail.com> wrote: >> >> manually running it through sudo slurmdbd -D /path/to/conf is very quick >> on my fresh install >> >> trying to start the slurmdbd through systemctl take 3 minutes and then >> crashes and fail >> >> Is there an alternative to systemctl to start the slurmdbd in the >> background ? >> >> But most importantly I wanted to know why it takes so long through >> systemctl. Maybe I can increase the timeout limit ? >> >> On Thu, May 30, 2024 at 11:54 PM Ryan Novosielski <novos...@rutgers.edu> >> wrote: >> >>> It may take longer to start than systemd allows for. How long does it >>> take to start from the command line? It’s common to need to run it manually >>> for upgrades to complete. >>> >>> -- >>> #BlackLivesMatter >>> ____ >>> || \\UTGERS, >>> |---------------------------*O*--------------------------- >>> ||_// the State | Ryan Novosielski - novos...@rutgers.edu >>> || \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ >>> RBHS Campus >>> || \\ of NJ | Office of Advanced Research Computing - MSB >>> A555B, Newark >>> `' >>> >>> On May 30, 2024, at 20:24, Radhouane Aniba via slurm-users < >>> slurm-users@lists.schedmd.com> wrote: >>> >>> Ok I made some progress here. >>> >>> I removed and purged slurmdbd mysql mariadb etc .. and started from >>> scratch. >>> I added the recommended mysqld requirements >>> >>> Started slurmdbd manually : sudo slurmdbd -D /path/to/conf and >>> everything worked well >>> >>> When I tried to start the service sudo systemctl start slurmdbd.service >>> it didnt work >>> >>> sudo systemctl status slurmdbd.service >>> ● slurmdbd.service - Slurm DBD accounting daemon >>> Loaded: loaded (/etc/systemd/system/slurmdbd.service; enabled; >>> vendor preset: enabled) >>> Active: failed (Result: timeout) since Fri 2024-05-31 00:21:30 UTC; >>> 2min 5s ago >>> Process: 6258 ExecStart=/usr/sbin/slurmdbd -D >>> /etc/slurm-llnl/slurmdbd.conf (code=exited, status=0/SUCCESS) >>> >>> May 31 00:20:00 hannibal-hn systemd[1]: Starting Slurm DBD accounting >>> daemon... >>> May 31 00:21:30 hannibal-hn systemd[1]: slurmdbd.service: start >>> operation timed out. Terminating. >>> May 31 00:21:30 hannibal-hn systemd[1]: slurmdbd.service: Failed with >>> result 'timeout'. >>> May 31 00:21:30 hannibal-hn systemd[1]: Failed to start Slurm DBD >>> accounting daemon. >>> >>> Even though it is the same command ?! >>> >>> Any idea ? >>> >>> -- >> *Rad Aniba, PhD* >> >> >> > > -- > *Rad Aniba, PhD* > > -- *Rad Aniba, PhD*
-- slurm-users mailing list -- slurm-users@lists.schedmd.com To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
