Error creating new record in DB: No valid id available, freeing object

Other OS or NAS discussions
Post Reply
User avatar
beigtapel3
Posts: 1
Joined: Sat Jun 30, 2018 9:05 pm
AV Hardware: LenovoEZ Media & Backup center

Error creating new record in DB: No valid id available, freeing object

Post by beigtapel3 » Sat Jun 30, 2018 9:15 pm

Hi.

I'm using LenovoEZ Media & Backup center as a home media center. Recently I noticed that I can't find latest added files (movies, music) from my Samsung Smart TV.

This is my twonkyvision-log.txt which is full of these lines:
2018-06-30 22:37:55:436 12283230 [Error] - LOG_DB: filedb_item_add : Error creating new record in DB: No valid id available, freeing object
2018-06-30 22:37:55:436 12280553 [Error] - LOG_DB: upnp_database_object_cache_add : Error adding object to database
2018-06-30 22:37:55:459 12283311 [Error] - LOG_DB: filedb_item_add : Error creating new record in DB: No valid id available, freeing object
2018-06-30 22:37:55:459 12280591 [Error] - LOG_DB: upnp_database_object_cache_add : Error adding object to database

Tried restarting Twonky server and Rescan Content Folders but no luck.

Here's my twonkyserver-log.txt after restart:
2018-06-30 23:12:36:653 12459732 [Important] - LOG_HTTP: rpc_stop_server : stopping server (rc=42)
2018-06-30 23:12:40:061 1276137 [Important] - LOG_SYSTEM: upnp_mediaserver_stop : media server stopped
2018-06-30 23:12:42:854 101329 [Startup] - LOG_SYSTEM: twonkylib_init : *** Starting TwonkyServer (Product Name:Twonky, Version:8.2.1-2, Build-date:Feb 8 2016) ***
2018-06-30 23:12:42:855 101399 [Startup] - LOG_SYSTEM: twonkylib_init : *** Platform:emc_centerpoint050_arm_eabi::emc-centerpoint050-arm-eabi-oem, Snapshot:Twonky_8.2.1-2_Release20160208 TA:00b40df013ad02c1fc714802a514611a52fe0a20 ***
2018-06-30 23:12:42:855 101302 [Startup] - LOG_SYSTEM: twonkylib_init : using logfile /mnt/pools/A/A0/MediaDB/twonky/twonkyvision-log.txt
2018-06-30 23:12:42:855 101284 [Startup] - LOG_SYSTEM: twonkylib_init : Executable file: /usr/local/twonky/twonkyserver
2018-06-30 23:12:42:855 101263 [Startup] - LOG_SYSTEM: twonkylib_init : Command Line Parameters: 6
2018-06-30 23:12:42:856 101255 [Startup] - LOG_SYSTEM: twonkylib_init : cmdline 1:-inifile
2018-06-30 23:12:42:856 101300 [Startup] - LOG_SYSTEM: twonkylib_init : cmdline 2:/mnt/system/media/twonky/twonkyvision-mediaserver.ini
2018-06-30 23:12:42:856 101255 [Startup] - LOG_SYSTEM: twonkylib_init : cmdline 3:-logfile
2018-06-30 23:12:42:856 101298 [Startup] - LOG_SYSTEM: twonkylib_init : cmdline 4:/mnt/pools/A/A0/MediaDB/twonky/twonkyvision-log.txt
2018-06-30 23:12:42:856 101255 [Startup] - LOG_SYSTEM: twonkylib_init : cmdline 5:-appdata
2018-06-30 23:12:42:857 101277 [Startup] - LOG_SYSTEM: twonkylib_init : cmdline 6:/mnt/pools/A/A0/MediaDB/twonky
2018-06-30 23:12:42:873 143046 [Startup] - LOG_SYSTEM: upnp_ini_file_read_properties_from_file : reading ini settings from /mnt/system/media/twonky/twonkyvision-mediaserver.ini
2018-06-30 23:12:42:877 142885 [Startup] - LOG_SYSTEM: upnp_ini_file_read_properties_from_file : friendlyname = %HOSTNAME%
2018-06-30 23:12:42:877 142866 [Startup] - LOG_SYSTEM: upnp_ini_file_read_properties_from_file : ip =
2018-06-30 23:12:42:878 142877 [Startup] - LOG_SYSTEM: upnp_ini_file_read_properties_from_file : nicrestart = 1
2018-06-30 23:12:42:958 131404 [Error] - LOG_RMEDIA: upnp_rm_init : wrong dbdir = /mnt/pools/A/A0/MediaDB/twonky
2018-06-30 23:12:42:958 131403 [Error] - LOG_RMEDIA: upnp_rm_init : use dbdir = /mnt/pools/A/A0/MediaDB//twonky
2018-06-30 23:12:48:030 7942844 [Error] - LOG_SYSTEM: upnp_accounting_license_twonky_load_locked : 0: 12001: /mnt/pools/A/A0/MediaDB/twonky/twonky.license

Post Reply