Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

s6-svscan/finish unable to run due to bad permissions #14

Closed
YipYup opened this issue Mar 14, 2023 · 12 comments · Fixed by #16
Closed

s6-svscan/finish unable to run due to bad permissions #14

YipYup opened this issue Mar 14, 2023 · 12 comments · Fixed by #16

Comments

@YipYup
Copy link
Contributor

YipYup commented Mar 14, 2023 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-libsecomp2: executing... 
[cont-init.d] 00-libsecomp2: exited 0.
[cont-init.d] 10-timestamp-set-utc: executing... 
[cont-init.d] 10-timestamp-set-utc: exited 0.
[cont-init.d] 30-get-beastfeeder-dev: executing... 
[cont-init.d] 30-get-beastfeeder-dev: exited 0.
[cont-init.d] 40-save-recv_host-ip: executing... 
[Tue Mar 14 01:57:42 UTC 2023][skysquitter/40-save-recv_host-ip] The IP address for readsb cannot be resolved. We will continue to try up to 60 seconds.
[Tue Mar 14 01:58:43 UTC 2023][skysquitter/40-save-recv_host-ip] The IP address for readsb cannot be resolved after trying for 60 seconds. Is your Beast Source system available?
[cont-init.d] 40-save-recv_host-ip: exited 1.
s6-svscan: warning: unable to exec finish script .s6-svscan/finish: Permission denied
s6-svscan: warning: executing into .s6-svscan/crash
s6-svscan: fatal: unable to exec .s6-svscan/crash: Permission denied
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-libsecomp2: executing... 
[cont-init.d] 00-libsecomp2: exited 0.
[cont-init.d] 10-timestamp-set-utc: executing... 
[cont-init.d] 10-timestamp-set-utc: exited 0.
[cont-init.d] 30-get-beastfeeder-dev: executing... 
[cont-init.d] 30-get-beastfeeder-dev: exited 0.
[cont-init.d] 40-save-recv_host-ip: executing... 
[Tue Mar 14 01:58:49 UTC 2023][skysquitter/40-save-recv_host-ip] The IP address for readsb cannot be resolved. We will continue to try up to 60 seconds.
[Tue Mar 14 01:59:50 UTC 2023][skysquitter/40-save-recv_host-ip] The IP address for readsb cannot be resolved after trying for 60 seconds. Is your Beast Source system available?
[cont-init.d] 40-save-recv_host-ip: exited 1.
s6-svscan: warning: unable to exec finish script .s6-svscan/finish: Permission denied
s6-svscan: warning: executing into .s6-svscan/crash
s6-svscan: fatal: unable to exec .s6-svscan/crash: Permission denied
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-libsecomp2: executing... 
[cont-init.d] 00-libsecomp2: exited 0.
[cont-init.d] 10-timestamp-set-utc: executing... 
[cont-init.d] 10-timestamp-set-utc: exited 0.
[cont-init.d] 30-get-beastfeeder-dev: executing... 
[cont-init.d] 30-get-beastfeeder-dev: exited 0.
[cont-init.d] 40-save-recv_host-ip: executing... 
[Tue Mar 14 01:59:57 UTC 2023][skysquitter/40-save-recv_host-ip] The IP address for readsb cannot be resolved. We will continue to try up to 60 seconds.
@YipYup
Copy link
Contributor Author

YipYup commented Mar 14, 2023

Ignore the "IP address for readsb cannot be resolved". I've fixed that locally, but what I'm reporting is the inability of the s6-svscan/crash to run.

s6-svscan: warning: executing into .s6-svscan/crash
s6-svscan: fatal: unable to exec .s6-svscan/crash: Permission denied

@kx1t
Copy link
Owner

kx1t commented Mar 15, 2023 •
edited
Loading

What are you running this on? Are you mapping any additional volumes?
Also, can you attach the new logs now you’ve resolved the ip address issues?

@YipYup
Copy link
Contributor Author

YipYup commented Mar 15, 2023

Here's my YML for the docker service:

################################################################################
# SkySquitter / SkySquitter.com
################################################################################
  skysquitter:
    image: ghcr.io/kx1t/docker-skysquitter
    tty: true
    container_name: skysquitter
    hostname: skysquitter
    restart: always
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
      - SYS_NICE
    networks:
      adsbnet:
        ipv4_address: 192.168.168.40
        aliases:
          - skysquitter
    environment:
      - CLOCK_DIFF_LIMIT=${SKYSQUITTER_CLOCK_DIFF_LIMIT}
      - MY_IP=${SKYSQUITTER_VPN_IP}
      - NTP_REFSERVER=${SKYSQUITTER_NTP_REFERENCE_SERVER}
      - PRUNE_INTERVAL=${SKYSQUITTER_PRUNE_INTERVAL}
      - PRUNE_SIZE=${SKYSQUITTER_PRUNE_SIZE}
      - RECV_HOST=${SKYSQUITTER_SOURCE_HOST}
      - RECV_PORT=${SKYSQUITTER_SOURCE_PORT}
      - SET_TIMESTAMP=${SKYSQUITTER_SET_TIMESTAMP}
      - TZ=${SKYSQUITTER_TIME_ZONE}
      - VERBOSELOGS=true
      - WG_PRIVKEY=${SKYSQUITTER_WG_PRIVKEY}
      - WG_PSK=${SKYSQUITTER_WG_PSK}
    volumes:
      - /opt/adsb/vol/skysquitter:/config
      - /lib/modules:/lib/modules
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
    tmpfs:
      - /run
      - /tmp
    depends_on:
      - readsb

@YipYup
Copy link
Contributor Author

YipYup commented Mar 15, 2023

Here are the logs:

root@host:/opt/adsb# docker logs skysquitter
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-libsecomp2: executing...  
[cont-init.d] 00-libsecomp2: exited 0.
[cont-init.d] 10-timestamp-set-utc: executing...  
[cont-init.d] 10-timestamp-set-utc: exited 0.
[cont-init.d] 30-get-beastfeeder-dev: executing...  
[cont-init.d] 30-get-beastfeeder-dev: exited 0.
[cont-init.d] 40-save-recv_host-ip: executing...  
[Wed Mar 15 21:59:20 UTC 2023][skysquitter/40-save-recv_host-ip] The IP address for readsb is 192.168.168.20
[cont-init.d] 40-save-recv_host-ip: exited 0.
[cont-init.d] 50-wireguard-setkeys: executing...  
[cont-init.d] 50-wireguard-setkeys: exited 0.
[cont-init.d] 60-start-wg: executing...  
[Wed Mar 15 21:59:20 UTC 2023][skysquitter/60-start-wg] Warning: `/config/wg0.conf' is world accessible
[Wed Mar 15 21:59:20 UTC 2023][skysquitter/60-start-wg] [#] ip link add wg0 type wireguard
[Wed Mar 15 21:59:20 UTC 2023][skysquitter/60-start-wg] [#] wg setconf wg0 /dev/fd/63
[Wed Mar 15 21:59:20 UTC 2023][skysquitter/60-start-wg] [#] ip -4 address add 10.9.2.x dev wg0
[Wed Mar 15 21:59:21 UTC 2023][skysquitter/60-start-wg] [#] ip link set mtu 1420 up dev wg0
[Wed Mar 15 21:59:21 UTC 2023][skysquitter/60-start-wg] [#] ip -4 route add [10.9.2.1/32](http://10.9.2.1/32) dev wg0
[Wed Mar 15 21:59:21 UTC 2023][skysquitter/60-start-wg] WireGuard VPN brought up.
[cont-init.d] 60-start-wg: exited 0.
[cont-init.d] 70-check-beastsource: executing...  
[Wed Mar 15 21:59:21 UTC 2023][skysquitter/70-check-beastsource] readsb:30005 is now available -- your Beast Data source is ready
[cont-init.d] 70-check-beastsource: exited 0.
[cont-init.d] 71-check-destination-host: executing...  
[Wed Mar 15 21:59:25 UTC 2023][skysquitter/71-check-destination-host] Your SkySquitter Server at 10.9.2.1 can be pinged - we are now ready to start sending it data
[cont-init.d] 71-check-destination-host: exited 0.
[cont-init.d] done.
[services.d] starting services
s6-supervise beast-feeder: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise clockdiff-service: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise watchdog-log-pruner: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise feeder-watchdog: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise (child): fatal: unable to exec run: Permission denied
[services.d] done.
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise watchdog-log-pruner: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise clockdiff-service: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise beast-feeder: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise feeder-watchdog: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise watchdog-log-pruner: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise beast-feeder: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise clockdiff-service: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise feeder-watchdog: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise beast-feeder: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise clockdiff-service: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise watchdog-log-pruner: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise feeder-watchdog: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise beast-feeder: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise clockdiff-service: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise watchdog-log-pruner: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise feeder-watchdog: warning: unable to spawn ./run - waiting 10 seconds

@kx1t
Copy link
Owner

kx1t commented Mar 16, 2023 •
edited
Loading

This is very strange. We normally allow Docker/Docker-Compose to run its own network setup, but that doesn’t appear to be the issue here.

One of the tasks of s6 is to copy the run scripts from their services directory into its own runtime directory, ensure that the execution permissions are set, and then execute them. This appears to work fine for the startup processes in cont-init.d, but not for the runtime services in /etc/services.d/xxxxx/run

Is there anything non-standard on the host machine you run this on? Normal, Debian based machine (Ubuntu, RaspOS, etc)? Normal host machine file system (ext4 with normal permissions, etc)? And you aren’t using selinux, are you?

One thing you can try is to verify the permissions are propagated correctly. See example from my SkySquitter container, all these run files should have permissions u=rwx,go=rx:

 pi@heerlen:~$ docker exec -it ssq bash -c "ls -als /var/run/s6/services/*/run"
4 -rwxr-xr-x 1 root root 3552 Mar 15 16:44 /var/run/s6/services/beast-feeder/run
8 -rwxr-xr-x 1 root root 4707 Mar 15 16:44 /var/run/s6/services/clockdiff-service/run
8 -rwxr-xr-x 1 root root 5496 Mar 15 16:44 /var/run/s6/services/feeder-watchdog/run
4 -rwxr-xr-x 1 root root  121 Mar 15 16:44 /var/run/s6/services/s6-fdholderd/run
4 -rwxr-xr-x 1 root root 1302 Mar 15 16:44 /var/run/s6/services/watchdog-log-pruner/run

@YipYup
Copy link
Contributor Author

YipYup commented Mar 16, 2023 •
edited
Loading

Host is a Raspberry Pi 4B running Ubuntu Server 22.04 LTS aarch64.

root@docker-host:/opt/adsb# uname -a
Linux docker-host 5.15.0-1025-raspi #27-Ubuntu SMP PREEMPT Thu Feb 16 17:09:55 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

root@docker-host:/opt/adsb# lsb_release --all
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.2 LTS
Release:	22.04
Codename:	jammy

root@docker-host:/opt/adsb# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

root@docker-host:/opt/adsb# docker --version
Docker version 20.10.21, build 20.10.21-0ubuntu1~22.04.2

root@docker-host:/opt/adsb# docker-compose --version
docker-compose version 1.29.2, build unknown

root@docker-host:/opt/adsb# docker exec -it skysquitter bash -c "ls -als /var/run/s6/services/*/run"
4 -rwxr-xr-x 1 root root 3552 Mar 15 09:39 /var/run/s6/services/beast-feeder/run
8 -rwxr-xr-x 1 root root 4707 Mar 15 09:39 /var/run/s6/services/clockdiff-service/run
8 -rwxr-xr-x 1 root root 5496 Mar 15 09:39 /var/run/s6/services/feeder-watchdog/run
4 -rwxr-xr-x 1 root root  121 Mar 15 09:39 /var/run/s6/services/s6-fdholderd/run
4 -rwxr-xr-x 1 root root 1302 Mar 15 09:39 /var/run/s6/services/watchdog-log-pruner/run

@YipYup
Copy link
Contributor Author

YipYup commented Mar 16, 2023 

root@docker-host:/opt/adsb# fdisk -l

Disk /dev/mmcblk0: 238.3 GiB, 255869321216 bytes, 499744768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb0a6845e

Device         Boot  Start       End   Sectors  Size Id Type
/dev/mmcblk0p1 *      2048    526335    524288  256M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      526336 499744734 499218399  238G 83 Linux

root@docker-host:/opt/adsb# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           781M  4.8M  777M   1% /run
/dev/mmcblk0p2  235G  9.3G  216G   5% /
tmpfs           3.9G     0  3.9G   0% /dev/shm
# NOTE: Docker Overlay filesystems excluded...
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/mmcblk0p1  253M  228M   25M  91% /boot/firmware
tmpfs           781M  4.0K  781M   1% /run/user/0

@kx1t
Copy link
Owner

kx1t commented Mar 16, 2023 •
edited
Loading

Yeah this looks all perfectly normal. You’re using the same version Linux and the same hardware I’m running this on.

I’ve done some googling on the error, and all I come across for your issue is that it could be related to the permissions of the process that runs Docker in Linux, for example in SeLinux. But that’s obviously not the case for you. You’re also not out of disk space.

I assume you’re not out of RAM
Memory either?

TBH I’m a bit at a loss here…

@YipYup
Copy link
Contributor Author

YipYup commented Mar 16, 2023

Plenty of memory left over...

root@docker-host:/opt/adsb# free -h
               total        used        free      shared  buff/cache   available
Mem:           7.6Gi       964Mi       5.3Gi        60Mi       1.4Gi       6.3Gi
Swap:             0B          0B          0B

Not sure if it's related, but I came across a thread where others had similar run permission issues. There were a few suggestions for fixing it. One was to use some s6 "patches", essentially link and permission overrides that are in a tar file that can be extracted during build to fix the issue. Other suggestions were to change the name of the entrypoint file, and to change the tmpfs mount options. Maybe these will be of help?

just-containers/s6-overlay#158

@kx1t
Copy link
Owner

kx1t commented Mar 16, 2023

Can you try mounting your /run directory in tmpfs explicitly with exec permissions? For example:

    tmpfs:
      - /run:rw,nosuid,nodev,exec,relatime,size=256M
      - /tmp:rw,nosuid,nodev,noexec,relatime,size=128M

(Several of the parameters are probably not needed but won’t hurt either, I copied it from my own setup)

@YipYup
Copy link
Contributor Author

YipYup commented Mar 16, 2023

Before seeing your latest reply, here's what I tried, and the result:

    tmpfs:
      - /run:exec,size=64M
      - /tmp:exec,size=64M

Logs output:

root@docker-host:/opt/adsb# docker logs skysquitter
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-libsecomp2: executing... 
[cont-init.d] 00-libsecomp2: exited 0.
[cont-init.d] 10-timestamp-set-utc: executing... 
[cont-init.d] 10-timestamp-set-utc: exited 0.
[cont-init.d] 30-get-beastfeeder-dev: executing... 
[cont-init.d] 30-get-beastfeeder-dev: exited 0.
[cont-init.d] 40-save-recv_host-ip: executing... 
[Thu Mar 16 02:20:01 UTC 2023][skysquitter/40-save-recv_host-ip] The IP address for readsb is 192.168.168.20
[cont-init.d] 40-save-recv_host-ip: exited 0.
[cont-init.d] 50-wireguard-setkeys: executing... 
[cont-init.d] 50-wireguard-setkeys: exited 0.
[cont-init.d] 60-start-wg: executing... 
[Thu Mar 16 02:20:01 UTC 2023][skysquitter/60-start-wg] Warning: `/config/wg0.conf' is world accessible
[Thu Mar 16 02:20:01 UTC 2023][skysquitter/60-start-wg] [#] ip link add wg0 type wireguard
[Thu Mar 16 02:20:01 UTC 2023][skysquitter/60-start-wg] [#] wg setconf wg0 /dev/fd/63
[Thu Mar 16 02:20:02 UTC 2023][skysquitter/60-start-wg] [#] ip -4 address add 10.9.2.17 dev wg0
[Thu Mar 16 02:20:02 UTC 2023][skysquitter/60-start-wg] [#] ip link set mtu 1420 up dev wg0
[Thu Mar 16 02:20:02 UTC 2023][skysquitter/60-start-wg] [#] ip -4 route add 10.9.2.1/32 dev wg0
[Thu Mar 16 02:20:02 UTC 2023][skysquitter/60-start-wg] WireGuard VPN brought up.
[cont-init.d] 60-start-wg: exited 0.
[cont-init.d] 70-check-beastsource: executing... 
[Thu Mar 16 02:20:02 UTC 2023][skysquitter/70-check-beastsource] readsb:30005 is now available -- your Beast Data source is ready
[cont-init.d] 70-check-beastsource: exited 0.
[cont-init.d] 71-check-destination-host: executing... 
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/71-check-destination-host] Your SkySquitter Server at 10.9.2.1 can be pinged - we are now ready to start sending it data
[cont-init.d] 71-check-destination-host: exited 0.
[cont-init.d] done.
[services.d] starting services
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/clockdiff-service] Started as an s6 service; logging is verbose
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-watchdog] Started as an s6 service
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/watchdog-log-pruner] Started as an s6 service
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] Started as an s6 service; logging is verbose
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] SkySquitter Container Version: 221216-1625
[services.d] done.
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] Beast-Feeder Version: 221216-0038
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] Starting the Data Connector with the following command line:
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] /usr/local/bin/beast-feeder readsb 30005 10.9.2.1 11092 TRUE 400
touch: cannot touch '/run/lock/beast-feeder.up': No such file or directory
[ERROR] /run/s6/services/beast-feeder/run in line 70 when executing: touch /run/lock/beast-feeder.up
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] SKYSQUITTER BEAST-FEEDER
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] build 15.221216-0038.02
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] Configuration:
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] Recv host: readsb
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] Recv port: 30005
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] Dest host: 10.9.2.1
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] Dest port: 11092
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] Set Timestamp: True
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] Clock diff limit: 400ms
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] Init TCP connection to Receiver
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] Init UDP connection to Destination
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] Connect to Receiver
[Thu Mar 16 02:20:06 UTC 2023][skysquitter/ssq-feeder] Start listening...
[Thu Mar 16 02:20:07 UTC 2023][skysquitter/clockdiff-service] Clock drift for gpsdntpd
: 0 msec/0 msec

This particular part from the above appears to have failed:

touch: cannot touch '/run/lock/beast-feeder.up': No such file or directory
[ERROR] /run/s6/services/beast-feeder/run in line 70 when executing: touch /run/lock/beast-feeder.up

@YipYup
Copy link
Contributor Author

YipYup commented Mar 16, 2023

So it seems the touch command fails because the directory doesn't exist.

root@skysquitter:/run# ls -alh
total 8.0K
drwxr-xr-x 3 root root   80 Mar 16 02:26 .
drwxr-xr-x 1 root root 4.0K Mar 16 02:26 ..
-rw-r--r-- 1 root root   21 Mar 16 02:36 clockdiff.status
drwxr-xr-x 8 root root  160 Mar 16 02:26 s6

This was referenced Mar 16, 2023
Merged
Merged
@kx1t kx1t closed this as completed in #16 Mar 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update docker-compose.yml
2 participants
@YipYup @kx1t