[SOLVED] lxc-start since last upgrade in -current, reproducible error

mralk3 · 11-17-2015, 06:34 PM

This error is not keeping me from using LXC in any way. Everything seems to operate as usual. I am using a network bridge with wifi. It is set up using proxy_arp =1 and ip_forward = 1. All of my containers are running either Slackware{,64} or Slackware{,64}-current. I did google this but I found next to no information with various queries. Whether it is a bug or a misconfiguration, I thought should ask about it here.

What exactly does this output mean?

Code:

# lxc-stop -k -n slackrepo ; lxc-start -n slackrepo 
lxc-start: utils.c: setproctitle: 1461 Invalid argument - setting cmdline failed

/var/log/lxc/slackrepo.log

Code:

lxc-start 1447805972.561 ERROR    lxc_utils - utils.c:setproctitle:1461 - Invalid argument - setting cmdline failed
lxc-start 1447806400.206 ERROR    lxc_utils - utils.c:setproctitle:1461 - Invalid argument - setting cmdline failed

mancha · 11-17-2015, 06:56 PM

LXC is complaining that it's unable to make certain prctl calls. The operative effect seems to be that LXC is unable to set the process titles. How serious is this? I'd have to review LXC code more closely but at first glance doesn't seem too worrisome.

In order to enable these prctl calls you should ask Pat to set CONFIG_CHECKPOINT_RESTORE in Slackware-current kernels (see: commit).

--mancha

chris.willing · 11-17-2015, 07:01 PM

See:
https://lists.linuxcontainers.org/pi...er/010409.html

mralk3 · 11-17-2015, 07:04 PM

Thanks for the quick responses. I thought it was harmless, this just confirms it.