[BUG] Webserver not starting after upgrade to 1.4.0

[Bart1909]

After updating to 1.4.0 the web server will not start. Docker-Output is:

broker_1     | 1:C 07 Apr 2021 12:41:45.274 # Redis version=6.0.12, bits=32, commit=00000000, modified=0, pid=1, just started
broker_1     | 1:C 07 Apr 2021 12:41:45.274 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
webserver_1  | Paperless-ng docker container starting...
webserver_1  | creating directory /tmp/paperless
broker_1     | 1:M 07 Apr 2021 12:41:45.280 # Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with 'noeviction' policy now.
broker_1     | 1:M 07 Apr 2021 12:41:45.281 * Running mode=standalone, port=6379.
broker_1     | 1:M 07 Apr 2021 12:41:45.281 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
broker_1     | 1:M 07 Apr 2021 12:41:45.281 # Server initialized
broker_1     | 1:M 07 Apr 2021 12:41:45.281 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
broker_1     | 1:M 07 Apr 2021 12:41:45.283 * Loading RDB produced by version 6.0.12
broker_1     | 1:M 07 Apr 2021 12:41:45.283 * RDB age 20 seconds
broker_1     | 1:M 07 Apr 2021 12:41:45.283 * RDB memory usage when created 0.63 Mb
broker_1     | 1:M 07 Apr 2021 12:41:45.283 * DB loaded from disk: 0.000 seconds
broker_1     | 1:M 07 Apr 2021 12:41:45.283 * Ready to accept connections
webserver_1  | Waiting for PostgreSQL to start...
webserver_1  | Apply database migrations...
webserver_1  | sudo: unable to get time of day: Operation not permitted
webserver_1  | sudo: error initializing audit plugin sudoers_audit
webserver_1  | Waiting for PostgreSQL to start...
webserver_1  | Apply database migrations...
webserver_1  | sudo: unable to get time of day: Operation not permitted
webserver_1  | sudo: error initializing audit plugin sudoers_audit
paperless_webserver_1 exited with code 1
webserver_1  | Waiting for PostgreSQL to start...
webserver_1  | Apply database migrations...
webserver_1  | sudo: unable to get time of day: Operation not permitted
webserver_1  | sudo: error initializing audit plugin sudoers_audit
paperless_webserver_1 exited with code 1
webserver_1  | Waiting for PostgreSQL to start...
webserver_1  | Apply database migrations...
webserver_1  | sudo: unable to get time of day: Operation not permitted
webserver_1  | sudo: error initializing audit plugin sudoers_audit
paperless_webserver_1 exited with code 1
webserver_1  | Waiting for PostgreSQL to start...
webserver_1  | Apply database migrations...
webserver_1  | sudo: unable to get time of day: Operation not permitted
webserver_1  | sudo: error initializing audit plugin sudoers_audit
paperless_webserver_1 exited with code 1

[jonaswinkler]

on the host.

I totally did not get that and reacted too quickly with 1.4.2. Oh well.

[sitarane]

I was waiting on the update to have a testable environment. I'll update if we throw the towel in. Are we at that point yet?

[WhiteHatTux]

@sitarane With all the research I have done on the issue I was not able to find a different solution. It is fairly easy to go back to the previous libseccomp on the host and reproduce the error. I have done the back and forth a few time successfully. I would suggest you upgrade to the new libseccomp, as I don't see any way of this getting fixed otherwise.

[Radioaktivman]

Hi i found this this which solved the problem on my Rpi4

[Babalion]

@Radioaktivman thank you very much, this worked flawlessly for me!