cisco IR1101-K9 write memory command

[georgesofroniadis]

hello all,

Today i am facing an issue with write memory command. i configured the cisco router from console port and no issue to save the configuration.

now i am tryin to save the config via ssh port  but nothing happened and seems that is freezed . 

System image file is "bootflash:ir1101-universalk9.17.03.06.SPA.bin"

Do you have any idea?

[marce1000]

                - Check logs (from a  console session) when write memory is tried through an  SSH session.

 M.

[georgesofroniadis]

Seems like start up config is corrupted..
Mar 4 2024 16:48:22.728 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '822', automatic retry. -Process= "SSH Process", ipl= 0, pid= 807
Mar 4 2024 16:48:23.277 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '822', automatic retry. -Process= "SSH Process", ipl= 0, pid= 811
Mar 4 2024 16:48:26.821 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '824', automatic retry. -Process= "SSH Process", ipl= 0, pid= 650
Mar 4 2024 16:48:33.395 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '815', automatic retry. -Process= "SSH Process", ipl= 0, pid= 786
Mar 4 2024 16:48:37.769 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '805', automatic retry. -Process= "SSH Process", ipl= 0, pid= 809
Mar 4 2024 16:48:42.473 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '818', automatic retry. -Process= "SSH Process", ipl= 0, pid= 748
Mar 4 2024 16:48:43.453 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '818', automatic retry. -Process= "SSH Process", ipl= 0, pid= 785
Mar 4 2024 16:48:44.417 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '818', automatic retry. -Process= "SSH Process", ipl= 0, pid= 806
Mar 4 2024 16:48:47.371 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '816', automatic retry. -Process= "SSH Process", ipl= 0, pid= 780
Mar 4 2024 16:48:48.633 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '816', automatic retry. -Process= "SSH Process", ipl= 0, pid= 794
Mar 4 2024 16:48:52.730 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '814', automatic retry. -Process= "SSH Process", ipl= 0, pid= 807
Mar 4 2024 16:48:53.278 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '814', automatic retry. -Process= "SSH Process", ipl= 0, pid= 811
Mar 4 2024 16:48:56.822 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '819', automatic retry. -Process= "SSH Process", ipl= 0, pid= 650
Mar 4 2024 16:49:03.408 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '818', automatic retry. -Process= "SSH Process", ipl= 0, pid= 786
Mar 4 2024 16:49:07.768 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '804', automatic retry. -Process= "SSH Process", ipl= 0, pid= 809
Mar 4 2024 16:49:12.474 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '821', automatic retry. -Process= "SSH Process", ipl= 0, pid= 748
Mar 4 2024 16:49:13.453 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '821', automatic retry. -Process= "SSH Process", ipl= 0, pid= 785
Mar 4 2024 16:49:14.417 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '821', automatic retry. -Process= "SSH Process", ipl= 0, pid= 806
Mar 4 2024 16:49:17.393 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '814', automatic retry. -Process= "SSH Process", ipl= 0, pid= 780
Mar 4 2024 16:49:18.632 UTC: %PARSER-6-WMLRETRY: Write memory lock currently held by pid '814', automatic retry. -Process= "SSH Process", ipl= 0, pid= 794

this is the logs that i got filter by Write memory

[marce1000]

                           - FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvp97187
  Which  you are experiencing too ; since the bug report mentions power cycle as the only workaround you may try to export the running config to an external tftp server first (e.g.) and import (again) after the power cycle was done , 

 M.

[georgesofroniadis]

i will try it tommorow since nobody is physicaly on the router

Thanks a lot!

[marce1000]

                     >...i will try it tommorow since nobody is physicaly on the router
  - Actually you can apparently still execute  a write memory from the console too , before the power cycle , 

 M.

[georgesofroniadis]

The issue is resolved! 

i execute the sh users command

and then clear line ....  there was a plenty of remote connections and cleared them and works!

Thanks for your input!

[Georg Pauwen]

Hello,

post the full running config of your router. Sounds like an authentication/authorization problem...

[georgesofroniadis]

hello ,

i am not authorised to share the full config since include sensitive data!

Thanks a lot!