Your message dated Wed, 17 Aug 2016 18:30:19 +0100
with message-id
<1471455019.2088704.698237537.458c1...@webmail.messagingengine.com>
and subject line Re: Bug#834551: redis-server: Redis fails to start directly
after install
has caused the Debian Bug report #834551,
regarding redis-server: Redis fails to start directly after install
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
834551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834551
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: redis-server
Version: 2:3.2.3-1
Severity: important
Dear Maintainer,
On a system on which Redis hasn't been installed before, Redis fails to start
directly after install:
Created symlink /etc/systemd/system/redis.service â
/lib/systemd/system/redis-server.service.
Created symlink
/etc/systemd/system/multi-user.target.wants/redis-server.service â
/lib/systemd/system/redis-server.service.
Job for redis-server.service failed because the control process exited with
error code.
See "systemctl status redis-server.service" and "journalctl -xe" for details.
invoke-rc.d: initscript redis-server, action "start" failed.
â redis-server.service - Advanced key-value store
Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor
preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2016-08-17
01:13:49 CEST; 13ms ago
Docs: http://redis.io/documentation,
man:redis-server(1)
Process: 14426 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf
(code=exited, status=226/NAMESPACE)
Process: 14389 ExecStartPre=/bin/run-parts --verbose
/etc/redis/redis-server.pre-up.d (code=exited, status=226/NAMESPACE)
Aug 17 01:13:49 illium systemd[1]: Failed to start Advanced key-value store.
Aug 17 01:13:49 illium systemd[1]: redis-server.service: Unit entered faile...e.
Aug 17 01:13:49 illium systemd[1]: redis-server.service: Failed with result...'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package redis-server (--configure):
Trying to start redis manually after dpkg exited result in the same error. This
is probably an error in the init script?
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages redis-server depends on:
ii adduser 3.115
ii init-system-helpers 1.42
ii libc6 2.23-4
ii libjemalloc1 3.6.0-9
ii redis-tools 2:3.2.3-1
redis-server recommends no packages.
redis-server suggests no packages.
-- Configuration Files:
/etc/redis/redis.conf [Errno 13] Permission denied: u'/etc/redis/redis.conf'
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Lars,
> > Isn't "Stale file handle" something to do with NFS...? I've not seen it
> > in many years.. Does that ring any bells for your configuration?
>
> That was it... I had a stale NFS mount somewhere in /mnt/. After
> unmounting the NFS mount, Redis starts up without any problems.
Yay!
> I don't get why this (seemingly unrelated) issue caused Redis to fail to
> start though.
If I were to guess, it's likely that the namespace stuff checks all the
current filesystems. Or systemd explicitly does as part of its hardening
feature set.. I'm not sure, and I guess its out of the domain of the redis
package itself.
> Anyway, thanks a lot for your help. And sorry for wasting your time on
> something that was not a bug after all...
No need to apologise; Glad we managed to solve it. :)
(Closing bug in BCC.)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` [email protected] / chris-lamb.co.uk
`-
--- End Message ---
