Exec Format Error

Lijsterbes

I wrote a frontend:

lijster@lijsterbes [SSH] ~ % cat /etc/66/service/nohang                
[Main]
Type = classic
Version = 0.0.1
Description = "nohang OOM killer"
User = ( root )


[Start]
Build = custom
Execute = ( /usr/bin/execl-cmdline -s { /usr/bin/nohang ${Args} } )

[Environment]
Args=!-c /etc/nohang/the-cloud-nohang.conf --monitor

which I enabled and started. But then I run

lijster@lijsterbes [SSH] ~ % sudo 66 status nohang                              
[sudo] password for lijster: 
Name                  : nohang
Version               : 0.0.1
In tree               : global
Status                : enabled, down (exitcode 126) 0 seconds, normally up, want up, ready 0 seconds
Type                  : classic
Description           : nohang OOM killer
Part of               : None
Notify                : 0
Max death             : 5
Earlier               : 0
Source                : /etc/66/service/nohang
Live                  : /run/66/scandir/0/nohang
Dependencies          : nohang-log
Required by           : None
Optional dependencies : None
Start script          : 
                         /usr/bin/execl-cmdline { /usr/bin/nohang ${Args} } 
Stop script           : 
                        None
Environment source    : /etc/66/conf/nohang/0.0.1
Environment file      : environment variables from: /etc/66/conf/nohang/0.0.1/.nohang
                        Args=!-c /etc/nohang/the-cloud-nohang.conf

StdIn                 : s6log:/run/66/scandir/0/fdholder
StdOut                : s6log:/var/log/66/nohang
StdErr                : inherit:/var/log/66/nohang
Logger name           : nohang-log
Logger file           : 
66-execute: info: Starting service: nohang
66-execute: fatal: unable to exec /run/66/state/0/nohang/run.user: Exec format error
66-execute: info: Starting service: nohang
66-execute: fatal: unable to exec /run/66/state/0/nohang/run.user: Exec format error
66-execute: info: Starting service: nohang
66-execute: fatal: unable to exec /run/66/state/0/nohang/run.user: Exec format error
66-execute: info: Starting service: nohang
66-execute: fatal: unable to exec /run/66/state/0/nohang/run.user: Exec format error
66-execute: info: Starting service: nohang
66-execute: fatal: unable to exec /run/66/state/0/nohang/run.user: Exec format error

which is puzzling. I then do

lijster@lijsterbes [SSH] ~ % cat /run/66/state/0/nohang/run.user
 /usr/bin/execl-cmdline { /usr/bin/nohang ${Args} }

which differs from its properly working brothers mostly by a shebang line:

lijster@lijsterbes [SSH] ~ % cat /run/66/state/0/dhcpcd/run.user
#!/usr/bin/execlineb -P
 /usr/bin/execl-cmdline -s { /usr/bin/dhcpcd -B -f /etc/dhcpcd.conf } 
lijster@lijsterbes [SSH] ~ % cat /run/66/state/0/openntpd/run.user
#!/usr/bin/execlineb -P

    /usr/bin/execl-toc -d /var/empty/openntpd
    /usr/bin/execl-toc -d /run/openntpd
    /usr/bin/execl-cmdline -s { /usr/bin/ntpd -d }

But I don't know what to manipulate [or indeed, what I am doing wrong] to unfuck this problem. Any ideas?

eric

This is intended. You set:

[Start]
Build = custom

66 expect a shebang entry as you ask for a different format than the default which is execline. But what is your version of 66 (66 version output please)?
Anyway, if you write your script in execline, just remove the Build key.
If you want to write your script with another language use Build = custom then begin your script with the correct shebang like:

Execute = (#!/usr/bin/sh
/usr/bin/nohang ${Args}

A none existing shebang entry will produce the Exec format error.

Note

when you use the default format, you don't need to put the shebang, 66 will do it for you that why you have a difference between your run.user scripts.
If you want to quickly view all information available for a service just do:

# 66 resolve nohang

and look for the fields e.g. run, run_user.

Lijsterbes

That was quick!

lijster@lijsterbes [SSH] ~ % sudo 66 version version: info: 0.8.0.1

I tried removing the Build key and restarted the service, even disabled-stopped-enabled-started the service, but so far no change in behavior.

`lijster@lijsterbes [SSH] ~ % sudo 66 resolve nohang
name : nohang
description : nohang OOM killer
version : 0.0.1
type : 0
notify : 0
maxdeath : 5
earlier : 0
copyfrom : None
intree : None
ownerstr : 0
owner : 0
treename : global
user : root
inns : None
enabled : 1
islog : 0
home : /var/lib/66/
frontend : /etc/66/service/nohang
servicedir : /var/lib/66/system/service/svc/nohang
depends : nohang-log
requiredby : None
optsdeps : None
contents : None
ndepends : 1
nrequiredby : 0
noptsdeps : 0
ncontents : 0
run : #!/usr/bin/execlineb -P
importas -D2 VERBOSITY VERBOSITY
/usr/libexec/66-execute -v${VERBOSITY} start nohang

run_user : /usr/bin/execl-cmdline { /usr/bin/nohang ${Args} }

run_build : custom
run_runas : None
finish : None
finish_user : None
finish_build : None
finish_runas : None
timeoutstart : 0
timeoutstop : 0
down : 0
downsignal : 0
livedir : /run/66/
status : /var/lib/66/system/.resolve/service/nohang/state/status
servicedir : /run/66/state/0/nohang
scandir : /run/66/scandir/0/nohang
statedir : /run/66/state/0/nohang/state
eventdir : /run/66/state/0/nohang/event
notifdir : /run/66/state/0/nohang/notif
supervisedir : /run/66/state/0/nohang/supervise
fdholderdir : /run/66/scandir/0/fdholder
oneshotddir : /run/66/scandir/0/oneshotd
logname : nohang-log
logbackup : 3
logmaxsize : 1000000
logtimestamp : 3
logwant : 1
logrun : #!/usr/bin/execlineb -P
/usr/libexec/66-execute start nohang-log

logrun_user : #!/usr/bin/execlineb -P
s6-log -d3 n3 s1000000 /var/log/66/nohang

logrun_build : None
logrun_runas : s6log
logtimeoutstart : 0
logtimeoutstop : 0
env : Args=!-c /etc/nohang/the-cloud-nohang.conf

envdir : /etc/66/conf/nohang
env_overwrite : 0
configure : None
directories : None
files : None
infiles : None
ndirectories : 0
nfiles : 0
ninfiles : 0
stdintype : 3
stdindest : /run/66/scandir/0/fdholder
stdouttype : 3
stdoutdest : /var/log/66/nohang
stderrtype : 5
stderrdest : /var/log/66/nohang
rversion : 0.8.0.1`

and

lijster@lijsterbes [SSH] ~ % cat /run/66/state/0/nohang/run.user /usr/bin/execl-cmdline { /usr/bin/nohang ${Args} }

eric

Please take care of your writing to respect markdown format.
I still see:

run_build : custom

So change the nohang frontend file removing the key and do:

# 66 reconfigure nohang

to apply the frontend file change. Check again if you want your resolve file doing again 66 resolve nohang

Lijsterbes

That did the trick! The service is running smoothly now.

Thank you!

vixalien

hey eric. do you plan to reduce the need of the reconfigure parse resolve and remove commands. I think the documentation would be nice to tell us why they are needed.

Currently, I'm used to just doing service cupsd start service cupsd stop and don't need to worry about all these different parsing commands.

eric

@vixalien
In practice, you don't need to take care about the parse, resolve, remove command. The only one you may need it's reconfigure and only if something change at the frontend file of the service. parse and resolve are admin command and remove can be used to clean up your service set (Why to keep a service which is not used), but this is not mandatory. You can leave the service as it even if you don't use it.
As the documentation of the start say:

If the service has never been parsed, the start command will parse it

Same thing for the enable command, it will parse the service if its was never used.

Note

The documentation surely need improvement, please don't hesitate to make MR about it.