Created attachment 170503 [details]
Dynagen sample config
dynagen-0.11.0_4 crashes with:
udakov@wst10sudakovva:~/dynagen % dynagen mpls1.net
Reading configuration file...
*** Dynagen has crashed ****
Please open a bug report against Dynagen at http://7200emu.hacki.at
Include a description of what you were doing when the error occured, your
network file, also any errors output by dynamips hypervisor, and the following traceback data:
Traceback (most recent call last):
File "/usr/local/bin/dynagen", line 2207, in <module>
File "/usr/local/bin/dynagen", line 1005, in import_config
config = self.open_config(FILENAME)
File "/usr/local/bin/dynagen", line 978, in open_config
res = config.validate(vtor, preserve_errors=True)
UnboundLocalError: local variable 'config' referenced before assignment
Press ENTER to exit
The config should be correct, I use it on an older system. Howerer, I am attaching it just in case.
Created attachment 181998 [details]
This is a patch for correct problem.
Created attachment 181999 [details]
Created attachment 182000 [details]
(In reply to Pavel Volkov from comment #1)
This patch fixes the immediate problem of dynagen crashing with a python error. Thank you for that.
Now the "dynamips -H 7200" process itself crashes with a bus error (FreeBSD 10.3-RELEASE-p18 amd64).
(In reply to vas from comment #4)
Hello. Please, set "autostart" to false. And start your router's manually. Step by step.
(In reply to Pavel Volkov from comment #5)
Actually, my Step 0 was to test RAM with memtest86. It's OK.
My Step 1 was to simplify the lab (see below). Anyway, dynamips crashes with a bus error (signal 10) as soon as I access the virtual router's console at "telnet localhost 2001".
autostart = false
model = 7200
workingdir = /usr/home/student/dynagen/work
image = /usr/home/student/dynagen/C7200-AD.BIN
npe = npe-400
ram = 190
mmap = false
console = 2001
model = 7200
Please note that I have removed all the autostart and idlepc stuff.
(In reply to vas from comment #6)
You right. It's dynamips problem, not dynagen. I don't know how to fix it yet.
Is this still relevant?
(In reply to Tobias C. Berner from comment #8)
> Is this still relevant?
Can you please wait 4-5 days for an answer?
(In reply to Gleb Popov from comment #10)
Nothing has changed, still crashes.
Could you regenerate the patch to apply to the current tree?
I've changed my job so this issue is not relevant to me any more. I think we can delete this port as useless.
Ok, I'll close it. Sorry for the long time it took for nothing to happen here.
(In reply to Tobias C. Berner from comment #14)
I did not mean closing just the PR. I meant deleting the port or marking it as BROKEN.
> Sorry for the long time it took for nothing to happen here.
NP, I was not enthusiastic enough to help revive the port, either. We now have more advanced Cisco lab environments.