Welcome, Guest. Please login or register.

Author Topic: DBD::mysql::db do failed: Data too long for column 'assettype  (Read 31 times)

eviltrooper

  • Newbie
  • *
  • Posts: 45
    • View Profile
Hello,

i have a problem with Nedi 1.6p3 i use the "ciscoeol" and want do update my Database.
but i become some error..

Code: [Select]
/var/www/nedi/nedi.pl -vv -Yam -a xx..xxx.xxx.xxx
Code: [Select]
WDEV:3825-xxx-01 written to nedi.devices
CHKP:Cisco cisco3825 is EoL, check PDID EOL7247INV :Device XXXXXXXX added to nedi.inventory
CHKP:0 matches found with NM-30DM= in ciscoeol.csv
INV :Module NM-30DM= 33508225 added to nediges.inventory
CHKP:0 matches found with NM-1CE1T1-PRI= in ciscoeol.csv
INV :Module NM-1CE1T1-PRI= XXXXXXXX added to nedi.inventory
CHKP:0 matches found with c3825 Motherboard with Gigabit Ethernet in ciscoeol.csv
DBD::mysql::db do failed: Data too long for column 'assettype' at row 1 at /var/www/nedi/inc/libdb.pm line 1671.
DBD::mysql::db do failed: Data too long for column 'assettype' at row 1 at /var/www/nedi/inc/libdb.pm line 1671.

anyone have an idea?

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2495
    • View Profile
    • NeDi
Re: DBD::mysql::db do failed: Data too long for column 'assettype
« Reply #1 on: March 21, 2017, 11:17:05 AM »
As a paying customer, you can contact me directly :-)

Some DB installations don't seem to just cut off strings longer than the DB field and just die.
I'll catch this error in the next patch, but you can simply comment line 4378 in libsnmp.pm to avoid it.
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

eviltrooper

  • Newbie
  • *
  • Posts: 45
    • View Profile
Re: DBD::mysql::db do failed: Data too long for column 'assettype
« Reply #2 on: March 21, 2017, 04:21:32 PM »
i give it a try..