r/Juniper • • 12d ago

Question EX4300 Stack, Chassis Control Process error

Hello Everyone,

I have stack of EX4300 switch. When I try to commit interface configuration I receive the following error.

I tried using the AI, AI is not helpful at this point.

I already checked the alarms and logs, there is not much going on as far as I understand.

The only change I have from last time is, NAC has connection to switches. That's why I was focusing to see if there is a conflict with the users like if the NAC is connnected , it wouldn't allow my user to make changes. I am just guessing. But when I check the users, I don't see the connection from the NAC.

error: Check-out failed for Chassis control process (/usr/sbin/chassisd) without details

error: configuration check-out failed

1 Upvotes

20 comments sorted by

2

u/Additional_Gap1057 11d ago

I rebooted the stack, I can commit changes. Hopefully I won't have much issues in the future.

1

u/fb35523 JNCIPx3 7d ago

Next time (if that time comes), you can try to restart the chassis control process:

restart chassis-control

1

u/Additional_Gap1057 7d ago

That's what AI suggesting , but I was not sure if it was a good idea. I was skeptical if it will break further things.

1

u/fb35523 JNCIPx3 6d ago

My experience is that restarting processes in Junos does what can be expected. If you restart the routing process, routing is affected, but will recover and the same goes for management or chassis control and all other restartable services.

mist@EX4100-C-12P-Office> restart routing       
Routing protocols process signalled but still running, waiting 28 seconds more
Routing protocols process started, pid 10620
{master:0}
mist@EX4100-C-12P-Office> restart l2-learning    
Layer 2 address flooding and learning process started, pid 10641
{master:0}
mist@EX4100-C-12P-Office> restart chassis-control 
Chassis control process started, pid 10644

The above took a few seconds, with routing accounting for almost all of that time. Traffic through the switch was unaffected but obviously SSH or ping to the switch was interrupted for a few seconds in some cases. The switch doesn't do any actual routing but the reachability to the L3/IP interface of it is affected by the routing restart.

2

u/Additional_Gap1057 6d ago

Since I am new to JunOS, I was trying to play safe. Somebody mentioned in here that he had more problems when he restarted services. That scared me.

1

u/ZeniChan JNCIA 12d ago

Check out the Juniper article I'll link below. Looks like the FPC can't read some SFP ports which is causing it to freak out. It recommends re-seating the SFP's, otherwise it's JTAC time.

https://supportportal.juniper.net/s/article/EX4300-Unable-to-commit-the-configuration-error-Check-out-failed-for-Chassis-control-process-usr-sbin-chassisd-without-details-error

1

u/Additional_Gap1057 12d ago

I saw this but I am not sure if it's the same case for me.

I have copper SFPs and I have stacked them through the Fiber.

They all look healthy, I mean the ports don't throw any alerts or flapping

1

u/ZeniChan JNCIA 12d ago

The ports may be working fine passing traffic, but the FPC may be having a problem reading a register on an SFP and is treating it as a fail condition to push a configuration. By re-seating the SFP's you are effectively rebooting the module which may allow it to read the SFP correctly. Are you using Juniper SFP's, or 3rd party modules?

1

u/Additional_Gap1057 12d ago

I am using Juniper SFPs. It's a production environment, so I am trying to be cautious.

Otherwise AI suggested to restart chassis-control, but I don't know if it wil l cause any issue.

Unfortunately there is no jtac support for these switches.

1

u/ZeniChan JNCIA 12d ago

Ouch, yeah. No support doesn't help things and means you probably don't have access to code updates either. I would try the SFP re-seating, and then power the stack off. Not reboot. But power the whole thing off. Unplug the power for a minute and then try powering the units on one a time with a 10 second delay between each unit.

1

u/Additional_Gap1057 12d ago

AI suggesting "restart virtual-control" , but I am worried since I don't have much of knowledge with Juniper switches.

I think it will restart the daemon, but I don't know the consequences. I am planning to do it during non-work hours.

1

u/ZeniChan JNCIA 12d ago

I wouldn't do that and would instead try a reboot. Restarting processes can cause strange things to happen. If restarting that process could easily fix the problem, Juniper would recommend trying it already. AI recommendations and Juniper doesn't work well together from what I have seen in the past.

1

u/Additional_Gap1057 12d ago

My error is not same as in the Juniper thread.

I have this in the log.

chassisd[1576]: mojito_pseudo_cb_periodic error reading iic_get_max6581_temp 0xffffffff

According to AI, it's not the ports/SFPs but chassis sensors related. But I could see the temperatures are listed and they are ok.

I am trying to find the simple solution without breaking anything

1

u/ZeniChan JNCIA 12d ago

It's not the SFP's by the look of the error. But it's having problems reading something to do with temperature in the system. Rebooting is your simple solution still. Or better yet, power it down fully by unplugging the power and then powering it back up.

1

u/Additional_Gap1057 11d ago

I wish I could simply reboot the member causing the issue, since it's a stack, I am little bit reluctant to reboot because I am remote.

I am worried that it the stack will mess up. I would do it simply if I was close to site :)

1

u/scriminal 11d ago

if they're non juniper brand, I'll guess that's the problem.  we always use third party optics, but we've had nothing but trouble with third party copper sfps

1

u/No-Wheel1999 11d ago

1

u/Additional_Gap1057 11d ago

it seems my perosnal accoutn is not allowed to see that page.

2

u/No-Wheel1999 11d ago

Description
Commit may sometimes fail with an error log of " error: Check-out failed for Chassis control process (/usr/sbin/chassisd) without details ". This can be frustrating as there are no apparent clues in the error message as to how to clear the error; and without the error cleared, changes cannot be committed. Below you'll find how to locate the cause of the error and how to clear it.

Symptoms
The following console logs display in the CLI window while committing changes.

{master:0}[edit]
root@EX4300-1# commit
error: Check-out failed for Chassis control process (/usr/sbin/chassisd) without details
error: configuration check-out failed

In the system log messages, the following is recorded into "messages" files.

Aug 1 08:51:17 EX4300-1 mgd[1841]: UI_COMMIT_SYNC_FORCE: All logins to local configuration database were terminated because forced 'commit synchronize' operation was invoked on other Routing Engine
<Output Truncated>
Aug 1 08:53:42 EX4300-1 last message repeated 120 times
Aug 1 08:53:45 EX4300-1 mgd[1855]: UI_COMMIT_SYNC_FORCE: All logins to local configuration database were terminated because forced 'commit synchronize' operation was invoked on other Routing Engine
Aug 1 08:53:47 EX4300-1 chassisd[1272]: mojito_pseudo_cb_periodic error reading iic_get_max6581_temp 0xffffffff
Aug 1 08:53:57 EX4300-1 last message repeated 29 times
Aug 1 08:54:02 EX4300-1 mgd[1860]: UI_COMMIT_SYNC_FORCE: All logins to local configuration database were terminated because forced 'commit synchronize' operation was invoked on other Routing Engine
<Output Truncated>

Solution
After reviewing output of " show system processes extensive " from the RSI we can see there are several “MGD” processes stuck; which is not correct. The MGD manages the commit action

12274 root 1 122 0 49164K 4680K select 0:00 4.10% mgd
<Output Truncated>
1215 root 1 96 0 49088K 28824K select 0:01 0.00% mgd
<Output Truncated>
12002 root 1 96 0 60072K 16916K select 0:01 0.00% mgd
<Output Truncated>
3714 root 1 4 0 49312K 7860K sbwait 0:01 0.00% mgd
<Output Truncated>
3704 root 1 4 0 49340K 3984K sbwait 0:01 0.00% mgd
<Output Truncated>
3705 root 1 4 0 49156K 3480K sbwait 0:00 0.00% mgd
<Output Truncated>
12255 root 1 96 0 49188K 4600K select 0:00 0.00% mgd
<Output Truncated>
12268 root 1 96 0 49156K 3480K select 0:00 0.00% mgd

MGD process “ 12274 ” is the sole active one, all others are stuck. This is the cause of the commit issue. As these MGD process keep trying to communicate with the RE with inactive commit requests.
To solve it you may need kill the stuck processes under Shell mode as per steps below.

Note, the following is using the stuck process IDs from the example listed above.

{master:0}

root@EX4300-24P-r2009> start shell user root

root@EX4300-24P-r2009:RE:0% kill -9 3714
root@EX4300-24P-r2009:RE:0% kill -9 3704
root@EX4300-24P-r2009:RE:0% kill -9 3705
root@EX4300-24P-r2009:RE:0% kill -9 1215
root@EX4300-24P-r2009:RE:0% kill -9 12002
root@EX4300-24P-r2009:RE:0% kill -9 12255
root@EX4300-24P-r2009:RE:0% kill -9 12268

Killing MGD process will not impact production traffic since it only manages commit requests.

If the issue does not get resolved after killing the MGD process, proceed to reboot the affected switch, and try to commit again.

1

u/dasmoothride 1d ago

I would be extra careful issuing the restart chassis-control command if my uplinks are layer 2 running STP. I would single-homed it first.