These are the channel logs matching your query /var/run/shepherd/socket
| 2025-10-24 | [18:18:22] <sneek> acrow, Rutherther says: I am not sure if someone properly addressed your problem. The /run/user/$USER is created by the pam rule, so no, you cannot install elogind as package and get that folder. But you dont need elogind in the first place. You can just set XDG_RUNTIME_DIR to a directory you prefer. People commonly use a directory under /tmp if they dont have logind. If shepherd is started with this env var, it will put its socket there. |
| 2025-10-13 | [08:38:15] <Rutherther> sneek: later tell acrow, I am not sure if someone properly addressed your problem. The /run/user/$USER is created by the pam rule, so no, you cannot install elogind as package and get that folder. But you dont need elogind in the first place. You can just set XDG_RUNTIME_DIR to a directory you prefer. People commonly use a directory under /tmp if they dont have logind. If shepherd is started with this env var, it will put its socket there. |
| 2025-04-21 | [02:29:18] <RavenJoad> This parse failure caused cuirass to "start" as seen by shepherd, but cuirass had exited, so the /var/run/cuirass/bridge socket was never created. |
| 2025-04-21 | [02:55:42] <apteryx> ah, it uses a %shepherd-socket-file parameter which defaults to "/var/run/shepherd/socket" |
| 2024-06-15 | [13:32:00] <fnat> A strace indicates there might be something wrong with my '/var/run/shepherd/socket', which I'm now investigating. |
| 2024-06-01 | [22:40:08] <fnat> Oh, ok, yeah, strace says something about '/var/run/shepherd/socket'. |
| 2024-06-01 | [23:07:37] <fnat> '/var/run/shepherd/socket' is regularly there, hm. |
| 2024-02-21 | [16:27:30] <PotentialUser-59> (reboot and halt both give error: /var/run/shepherd/socket: Connection refused) |
| 2022-11-27 | [17:32:24] <nckx> unmatched-paren: In theory, probably, by controlling access to /var/run/shepherd/socket & using herd --socket=, but in practice I would not trust it to be reliable/secure. |
| 2022-11-12 | [21:01:57] <mirai> error: connect: /var/run/shepherd/socket: No such file or directory |
| 2022-01-27 | [12:16:08] <attila_lendvai> i have a fully booted system where i get: error: connect: /var/run/shepherd/socket: No such file or directory. there are several matches in the IRC logs, but no solutions. |
| 2021-12-10 | [15:25:17] <attila_lendvai> how can i get "error: connect: /var/run/shepherd/socket: No such file or directory"? the dir is empty. the only unusual thing is that it's in a VM that got suspended with my laptop, and its time jumped. |
| 2021-09-10 | [11:24:51] <akib> It say: error: connect: /var/run/shepherd/socket: Connection refused |
| 2021-05-19 | [19:40:25] <apteryx> strange, when booting my operating system definition with the 'guix system vm' script, 'herd status' says "error: connect: /var/run/shepherd/socket: No such file or directory" |
| 2021-05-17 | [15:52:43] <fakhri> error: connect: /var/run/shepherd/socket: No such file or directory |
| 2020-12-28 | [02:32:37] <ride> error: connect: /var/run/shepherd/socket: No such file or directory |
| 2020-06-21 | [22:22:27] <cbaines> I get: error: connect: /var/run/shepherd/socket: Connection refused |
| 2020-05-21 | [18:23:45] <rekado> says ���System is powering down��� and then ���error: connect: /var/run/shepherd/socket: No such file or directory��� |
| 2019-08-27 | [15:13:40] <apteryx> example: docker start $container_id && docker exec -ti $container_id /run/current-system/profile/bin/bash --login -c 'herd status' returns: error: connect: /var/run/shepherd/socket: No such file or directory when the system is not yet initialized (that's my brute force way of telling for now) |
| 2019-06-20 | [18:12:30] <hulten> guix package -u as normal user ends with an error: connect: /var/run/shepherd/socket: Permission denied |
| 2019-06-20 | [18:24:01] <hulten> About the "/var/run/shepherd/socket: Permission denied", I forgot to mention that I am using Guix System, upgraded last night. |
| 2019-04-17 | [15:07:51] <nckx> root@zoltan /# herd status | error: connect: /var/run/shepherd/socket: No such file or directory |
| 2018-09-26 | [10:49:38] <roptat> but then in the container I get: error: connect: /var/run/shepherd/socket: No such file or directory |
| 2018-09-26 | [17:33:45] <civodul> roptat: i'm looking at the container issue: shepherd inside the container is stuck waiting for /var/run/dhclient.pid, which is why it doesn't set up its socket |
| 2018-09-12 | [17:51:53] <georges-duperon> roptat: For the full story: it then complained about /var/run/shepherd/socket missing. It turns out that one is created after all services are initialized, |
| 2017-09-12 | [17:13:05] <brendyn> when i run reboot or shutdown i get error: connect: /var/run/shepherd/socket |
| 2017-02-16 | [22:37:51] <roelj_> It seems to only listen on a TCP port, but the "herd" command expects it on a UNIX socket: error: connect: /var/run/shepherd/socket: No such file or directory |
| 2016-10-06 | [22:26:11] <fps> error: connect: /var/run/shepherd/socket: No such file or directory |
| 2016-10-05 | [06:19:32] <xd1le> this might have something to do with it, so I just tried to `sudo halt`, but it said "error: connect: /var/run/shepherd/socket: No such file or directory". When I look into /var/run, I see dmd/socket but no shepherd/socket, so could this be due to the dmd rename to shepherd? (Because I haven't updated in a while.) |
| 2016-08-05 | [09:57:31] <roptat> hi, I am running a container with my new openssh service, but when I try to get its status, I get "error: connect: /var/run/shepherd/socket: No such file or directory" |
| 2016-08-05 | [10:22:15] <alezost> hm, I don't know then. does /var/run/shepherd/socket exist? |
| 2016-03-20 | [14:28:34] <kristofer> sudo reboot says /var/run/dmd/socket not found - I have /var/run/shepherd/socket though |
| 2016-02-06 | [15:56:29] <petter> i'm trying to reboot but it's not going so well. I've tried "/run/booted-system/profile/sbin/reboot", but i get error: "/var/run/shepherd/socket: No such file or directory" |
| 2016-02-05 | [17:59:58] <calher> error: connect: /var/run/shepherd/socket: No such file or directory |
| 2016-02-03 | [17:00:35] <suitsmeveryfine> I just reconfigured my system and when I try to reboot or halt I get "error: connect: /var/run/shepherd/socket: file or directory does not exist" |
| 2016-02-03 | [17:06:38] <suitsmeveryfine> error: connect: /var/run/shepherd/socket: file or directory does not exist |
| 2016-02-03 | [20:21:24] <paroneayea> error: connect: /var/run/shepherd/socket: No such file or directory |
| 2016-02-01 | [01:21:06] <myglc2> Here is a dumb question... how do I reboot or shutdown my headless guixSD server. 'halt' give me 'error: connect: /var/run/shepherd/socket: No such file or directory' |