Hi
Running nav 3.6 on a Debian installation Its upgrade from nav 3.5.6
This error came when I'm trying to delete a device.
------------------------------------------------------
MOD_PYTHON ERROR
ProcessId: 16175 DocumentRoot: '/usr/share/nav/htdocs'
URI: '/seeddb/netbox/edit' Location: None Directory: '/usr/share/nav/htdocs/seeddb/' Filename: '/usr/share/nav/htdocs/seeddb/netbox' PathInfo: '/edit'
Phase: 'PythonHandler' Handler: 'seeddb'
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1537, in HandlerDispatch default=default_handler, arg=req, silent=hlist.silent)
File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1229, in _process_target result = _execute_target(config, req, object, arg)
File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1128, in _execute_target result = object(arg)
File "/usr/share/nav/htdocs/seeddb/seeddb.py", line 165, in handler output = editPage(req,pageList[table](),request,unicodeError)
File "/usr/share/nav/htdocs/seeddb/seeddb.py", line 461, in editPage status = page.delete(selected,status)
File "/usr/share/nav/htdocs/seeddb/seeddb.py", line 1617, in delete error += '%s is referenced in another table' % (self.name,)
AttributeError: pageNetbox instance has no attribute 'name'
------ end print ------
Med vennlig hilsen / Best Regards
Tor Pretorius Senior konsulent Data Instrumenttjenesten AS Frederik A. Dahlsvei 20 1432 Ås 91716759 / 64949840 www.it-as.nohttp://www.it-as.no/
On Thu, Oct 14, 2010 at 09:57:45AM +0200, Tor Pretorius wrote:
Hi
Running nav 3.6 on a Debian installation Its upgrade from nav 3.5.6
This error came when I'm trying to delete a device.
MOD_PYTHON ERROR
[snip]
File "/usr/share/nav/htdocs/seeddb/seeddb.py", line 1617, in delete error += '%s is referenced in another table' % (self.name,)
AttributeError: pageNetbox instance has no attribute 'name'
Seems like there are at least two bugs here. The delete operation caused a database integrity error, which should never happen when deleting an IP Device - all the database foreign keys should have cascading triggers that should resolve any integrity problems here.
The traceback indicates a typo in a variable name in the error handling code. Fixing the bug doesn't seem to make much of a difference in finding the integrity problem, since the output error message doesn't seem to convey any info about which reference caused the problem.
If you could please watch your postgresql logs while you retry the delete operation, it might give a better clue as to what's blocking the delete operation.
-
Morten Brekkevold -
Tor Pretorius