Skip to content

Container not restarted when changing configuration #1313

Closed

Description

@mattiaswal

Current Behavior

admin@wires-gp:/config/container/wires-gp/> set env EXTRA_ARGS value "--init-user --login x --password x"
admin@wires-gp:/config/container/wires-gp/> leave 
admin@wires-gp:/> 
admin@wires-gp:/> 
admin@wires-gp:/> container shell wires-race 
# 
# env
HOME=/stk-data
container=podman
TERM=xterm
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
SERVER_CONFIG=/stk-data/wires_normal_race.xml
PWD=/stk-data

The syslog during this:

Dec  8 10:11:53 wires-gp dnsmasq[2846]: using nameserver 172.31.11.11#53
Dec  8 10:11:53 wires-gp dnsmasq[2846]: using nameserver 172.31.11.12#53
Dec  8 10:11:53 wires-gp dnsmasq[2846]: using nameserver 172.31.11.11#53 for domain addiva.ad 
Dec  8 10:11:53 wires-gp dnsmasq[2846]: using nameserver 172.31.11.12#53 for domain addiva.ad 
Dec  8 10:11:53 wires-gp dnsmasq[2846]: read /etc/hosts - 2 names
Dec  8 10:12:19 wires-gp klishd[7759]: user "admin" commiting changes to running ...
Dec  8 10:12:19 wires-gp dagger[3604]: Evolved to generation 1
Dec  8 10:12:19 wires-gp confd[3604]: The new configuration has been applied.
Dec  8 10:12:19 wires-gp klishd[7759]: user "admin" committed changes to running.
Dec  8 10:12:22 wires-gp klishd[7759]: user "admin" leaving sysrepo session.
Dec  8 10:20:51 wires-gp klishd-listen[4075]: Service process for client was forked: 8575
Dec  8 10:20:51 wires-gp klishd[8575]: [8575]: Authenticated user 1000(admin), client PID 8573 
Dec  8 10:20:51 wires-gp klishd[8575]: user "admin" starting interactive sysrepo session.
Dec  8 10:23:21 wires-gp klishd[8575]: user "admin" leaving sysrepo session.
admin@wires-gp:~$ 

Expected Behavior

admin@infix-c0-ff-ee:/> show log
May 15 07:21:02 infix-c0-ff-ee container[3192]: Successfully created container test from curios-httpd-v24.03.0
- (press h for help or q to quit)

Steps To Reproduce

No response

Additional information

No response

Activity

  1. added
    bugSomething isn't working
    triagePending investigation & classification (CCB)
    on Dec 8, 2025
  2. troglobit commented on Dec 8, 2025

    @troglobit
    Contributor

    So you only changed environment?

  3. mattiaswal commented on Dec 8, 2025

    @mattiaswal
    ContributorAuthor

    I am not container-compatible, when i changed the correct container it detected the change at least, but:
    What i did was, change the correct container (wires-race), then removed wires-gp (was not running) from configuration (was not running).
    ec 8 10:26:59 wires-gp finit[1]: container:wires-race[8110], calling 'container -n wires-race stop' ... Dec 8 10:26:59 wires-gp confd[3604]: The new configuration has been applied. Dec 8 10:26:59 wires-gp klishd[8652]: user "admin" committed changes to running. Dec 8 10:27:09 wires-gp klishd[8652]: user "admin" commiting changes to running ... Dec 8 10:27:10 wires-gp dagger[3604]: Evolved to generation 3 Dec 8 10:27:10 wires-gp confd[3604]: The new configuration has been applied. Dec 8 10:27:10 wires-gp klishd[8652]: user "admin" committed changes to running. Dec 8 10:27:15 wires-gp klishd[8652]: user "admin" leaving sysrepo session. Dec 8 10:27:29 wires-gp finit[1]: Stopping container:wires-race[8110], sending SIGKILL ... Dec 8 10:27:29 wires-gp finit[1]: Stopped container:wires-race[8110] Dec 8 10:27:29 wires-gp wires-race[9035]: ^[[33mWARN^[[0m[0030] StopSignal SIGTERM failed to stop container wires-race in 30 seconds, resorting to SIGKILL Dec 8 10:27:29 wires-gp staticd[4399]: [EC 100663315] Thread Starvation: {(thread *)0xaaab20e81650 arg=0xaaab20ea6e40 timer r=-19.306 msg_client_connect_timer() &client->conn_retry_tmr from lib/mgmt_msg.c:632} was scheduled to pop greater than 4s ago Dec 8 10:27:29 wires-gp container[1]: Container wires-race config unchanged, skipping setup Dec 8 10:27:29 wires-gp finit[1]: Calling 'container -n wires-race start' ... Dec 8 10:27:29 wires-gp wires-race[9369]: Error: unable to start container "2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd": container 2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd must be in Created or Stopped state to be started: container state improper Dec 8 10:27:31 wires-gp finit[1]: Service container:wires-race[8110] died (with exit status: 125), restarting (retry in 2000 msec) (attempt: 1/10) Dec 8 10:27:31 wires-gp container[1]: Container wires-race config unchanged, skipping setup Dec 8 10:27:31 wires-gp finit[1]: Calling 'container -n wires-race start' ... Dec 8 10:27:32 wires-gp wires-race[9413]: Error: unable to start container "2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd": container 2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd must be in Created or Stopped state to be started: container state improper Dec 8 10:27:34 wires-gp finit[1]: Service container:wires-race[8110] died (with exit status: 125), restarting (retry in 2000 msec) (attempt: 2/10) Dec 8 10:27:34 wires-gp container[1]: Container wires-race config unchanged, skipping setup Dec 8 10:27:34 wires-gp finit[1]: Calling 'container -n wires-race start' ... Dec 8 10:27:34 wires-gp wires-race[9458]: Error: unable to start container "2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd": container 2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd must be in Created or Stopped state to be started: container state improper Dec 8 10:27:36 wires-gp finit[1]: Service container:wires-race[8110] died (with exit status: 125), restarting (retry in 2000 msec) (attempt: 3/10) Dec 8 10:27:36 wires-gp container[1]: Container wires-race config unchanged, skipping setup Dec 8 10:27:36 wires-gp finit[1]: Calling 'container -n wires-race start' ... Dec 8 10:27:36 wires-gp wires-race[9501]: Error: unable to start container "2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd": container 2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd must be in Created or Stopped state to be started: container state improper Dec 8 10:27:38 wires-gp finit[1]: Service container:wires-race[8110] died (with exit status: 125), restarting (retry in 2000 msec) (attempt: 4/10) Dec 8 10:27:38 wires-gp container[1]: Container wires-race config unchanged, skipping setup Dec 8 10:27:38 wires-gp finit[1]: Calling 'container -n wires-race start' ... Dec 8 10:27:38 wires-gp wires-race[9545]: Error: unable to start container "2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd": container 2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd must be in Created or Stopped state to be started: container state improper Dec 8 10:27:40 wires-gp finit[1]: Service container:wires-race[8110] died (with exit status: 125), restarting (retry in 2000 msec) (attempt: 5/10) Dec 8 10:27:41 wires-gp container[1]: Container wires-race config unchanged, skipping setup Dec 8 10:27:41 wires-gp finit[1]: Calling 'container -n wires-race start' ... Dec 8 10:27:41 wires-gp wires-race[9588]: Error: unable to start container "2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd": container 2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd must be in Created or Stopped state to be started: container state improper Dec 8 10:27:43 wires-gp finit[1]: Service container:wires-race[8110] died (with exit status: 125), restarting (retry in 5000 msec) (attempt: 6/10) Dec 8 10:27:43 wires-gp container[1]: Container wires-race config unchanged, skipping setup Dec 8 10:27:43 wires-gp finit[1]: Calling 'container -n wires-race start' ... Dec 8 10:27:43 wires-gp wires-race[9631]: Error: unable to start container "2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd": container 2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd must be in Created or Stopped state to be started: container state improper Dec 8 10:27:48 wires-gp finit[1]: Service container:wires-race[8110] died (with exit status: 125), restarting (retry in 5000 msec) (attempt: 7/10) Dec 8 10:27:48 wires-gp container[1]: Container wires-race config unchanged, skipping setup Dec 8 10:27:48 wires-gp finit[1]: Calling 'container -n wires-race start' ... Dec 8 10:27:48 wires-gp wires-race[9676]: Error: unable to start container "2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd": container 2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd must be in Created or Stopped state to be started: container state improper Dec 8 10:27:53 wires-gp finit[1]: Service container:wires-race[8110] died (with exit status: 125), restarting (retry in 5000 msec) (attempt: 8/10) Dec 8 10:27:54 wires-gp container[1]: Container wires-race config unchanged, skipping setup Dec 8 10:27:54 wires-gp finit[1]: Calling 'container -n wires-race start' ... Dec 8 10:27:54 wires-gp wires-race[9719]: Error: unable to start container "2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd": container 2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd must be in Created or Stopped state to be started: container state improper Dec 8 10:27:59 wires-gp finit[1]: Service container:wires-race[8110] died (with exit status: 125), restarting (retry in 5000 msec) (attempt: 9/10) Dec 8 10:27:59 wires-gp container[1]: Container wires-race config unchanged, skipping setup Dec 8 10:27:59 wires-gp finit[1]: Calling 'container -n wires-race start' ... Dec 8 10:27:59 wires-gp wires-race[9762]: Error: unable to start container "2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd": container 2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd must be in Created or Stopped state to be started: container state improper Dec 8 10:28:04 wires-gp finit[1]: Service container:wires-race[8110] died (with exit status: 125), restarting (retry in 5000 msec) (attempt: 10/10) Dec 8 10:28:04 wires-gp container[1]: Container wires-race config unchanged, skipping setup Dec 8 10:28:04 wires-gp finit[1]: Calling 'container -n wires-race start' ... Dec 8 10:28:04 wires-gp wires-race[9808]: Error: unable to start container "2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd": container 2e793c4efc414eb93c0581c215aa3c8367de3de8f43495bc8b837e90a3357dbd must be in Created or Stopped state to be started: container state improper Dec 8 10:28:09 wires-gp finit[1]: Service container:wires-race keeps crashing, not restarting. admin@wires-gp:~$
    Is it still my container-compliance that is the problem? Did i do anything wrong

  4. mattiaswal commented on Dec 8, 2025

    @mattiaswal
    ContributorAuthor

    Is the problem my rapid two-stage? configure wires-race, and remove wires-gp before wires-race was configured causing this?

  5. troglobit commented on Dec 8, 2025

    @troglobit
    Contributor

    Is the problem my rapid two-stage? configure wires-race, and remove wires-gp before wires-race was configured causing this?

    Possibly. I'll have to try it myself, but yeah there's a certain amount of async job going on in the background.

  6. mattiaswal commented on Dec 8, 2025

    @mattiaswal
    ContributorAuthor

    Reboot worked at least.

  7. added this to the Infix v26.01 milestone on Dec 15, 2025
  8. removed
    triagePending investigation & classification (CCB)
    on Dec 15, 2025
  9. added 2 commits that reference this issue on Feb 1, 2026
    70ae54c
    3d7fb59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions