digg_de's picture
digg_de - Fri, 2020/09/25 - 15:03

Hi,

I'm using a customized turnkey lamp 14 on my server. I have now upgrade this to debian 9 (stretch) and after to debian 10 (buster). It seems to work well. But the confconsole seems not working well. After starting the server there is only a quit button, no button for "Advanced Menu"? It is possible the update the confconsole for working on debian 10 or other hints for using on debian 10?

Thanks for help!

Bye g.g.

Forum: 
Support
Tags: 
lamp
confconsole
buster
digg_de's picture

digg_de - Fri, 2020/09/25 - 15:48

I found system message on bootup:

# systemctl status confconsole.service
* confconsole.service - LSB: Starts confconsole at boot time
   Loaded: loaded (/etc/init.d/confconsole; generated)
   Active: failed (Result: exit-code) since Fri 2020-09-25 14:40:50 CEST; 3min 36s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 408 ExecStart=/etc/init.d/confconsole start (code=exited, status=1/FAILURE)

Sep 25 14:40:50 test systemd[1]: Starting LSB: Starts confconsole at boot time...
Sep 25 14:40:50 test confconsole[408]: Starting confconsolesetterm: $TERM is not defined.
Sep 25 14:40:50 test systemd[1]: confconsole.service: Control process exited, code=exited, status=1/FAILURE
Sep 25 14:40:50 test systemd[1]: confconsole.service: Failed with result 'exit-code'.
Sep 25 14:40:50 test systemd[1]: Failed to start LSB: Starts confconsole at boot time.

and form network service:

# systemctl status networking.service
* networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-09-25 14:40:50 CEST; 5min ago
     Docs: man:interfaces(5)
  Process: 357 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
 Main PID: 357 (code=exited, status=1/FAILURE)

Sep 25 14:40:50 test ifup[357]: udhcpc: SIOCGIFINDEX: No such device
Sep 25 14:40:50 test ifup[357]: ifup: failed to bring up eth1
Sep 25 14:40:50 test systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Sep 25 14:40:50 test systemd[1]: networking.service: Failed with result 'exit-code'.
Sep 25 14:40:50 test systemd[1]: Failed to start Raise network interfaces.
Jeremy Davis's picture

Jeremy Davis - Mon, 2020/09/28 - 03:56

The "networking.service" doesn't actually do anything on TurnKey v16.x... But if you want it to report that it's running ok, please just comment out the 'eth1' interface in /etc/network/interfaces.

As I posted above, the Confconsole behaviour you've noted is expected. However, I'm not sure why you still have a confconsole.service (actually generated from /etc/init.d/confconsole)? It should have been removed as part of the upgrade process. Do you have the current Confconsole installed?

apt policy confconsole

The latest version is '2.0.1+9+g86f73bd' but you should have at least "2.0.1".

Regardless, if you wish to manually remove it, it's shouldn't cause any issues and can be done like this:

rm /etc/init.d/confconsole
Jeremy Davis's picture

Jeremy Davis - Mon, 2020/09/28 - 03:51

Re your note:

After starting the server there is only a quit button, no button for "Advanced Menu"

That is a change for v16.x. However, you are not the first to be unhappy with it.

FWIW in previous releases, Confconsole ran under it's own service. However, in Buster, I had huge issues getting Inithooks and Confconsole to play nicely together. They consistently wrestled for control of the terminal and that was causing big issues on firstboot. So what I did instead was removed the Confconsole service and made launching Confconsole the final action of Inithooks at boot time.

Considering that Confconsole runs as root and gives access to quite a lot of important stuff, not allowing "Advanced" by default without login is a reasonable default IMO. Although you are not the first to be unhappy with it and/or think that it is a problem. So perhaps we could provide better info to assist existing users to understand.

FWIW on a new instance, the first time you log in, it will automatically launch Confconsole (with the "Advanced" button) and the MOTD notes how to manually start it. If you want it to auto start on login, then you can do that via the autostart option in /etc/confconsole/confconsole.conf. Although as you've upgraded, you'll also need to copy the "confconsole-autorun" file into root's home. I.e.:

cp /usr/share/confconsole/autostart/confconsole-auto \
    /root/.bashrc.d/confconsole-auto
# should already be executable, but just in case
chmod +x /root/.bashrc.d/confconsole-auto

With that in place, the autostart setting in /etc/confconsole/confconsole.conf should be honored. (FWIW default is "once").

As I noted above though, you're not the first existing TurnKey user to report this. In retrospect, we should probably allow an option for returning to the previous default behaviour? In the meantime, it's pretty easy to manually do it if you wish.

Just change the Inithooks run file and exclude the (very poorly named) '--usage' switch. I.e. change:

confconsole --usage

to:

confconsole
digg_de's picture

digg_de - Mon, 2020/09/28 - 13:05

Hi Jeremy,

thanks a lot for your fast help! Your support is really excelent!

Yes you are right, the network.service doesn't matter.
Yes, I had the newest version but I need to remove the confconsole.service from the init.d manually.
And yes, I changed the option in the inithooks run file to load the "advanced menu". The idea is not bad to show it only after login, but I need a possility to change the IP and reboot the vm without root password.

Thanks a lot!
Bye g.g.

Jeremy Davis's picture

Jeremy Davis - Tue, 2020/09/29 - 02:23

Glad that works for you and you're back to where you want to be! :)

Add new comment