I've had similar issues. The daemon is just trying to map your ports automatically on your router. Sometimes this works, sometimes it doesn't. It's a harmless message. You can try disabling uPnP on your router to see if that gets rid of the message.
'UPnP device' error when running monerod
mountainman posted this 8 years ago
SOLVED: Was running bitmonero on 32-bit Ubuntu. Fixed when changing OS to 64 bit.
EDIT: Initial post indicated this was a UPnP issue, which it likely is not. I've updated the post below to what I now think is the problem.
I am trying to set up a Monero node (compiled from source Sept 7th). The blockchain seems to have been only partially synced. In my bitmonerod log this is repeating non-stop:
IN EDIT: Update log file excerpt below after running at log level 3.
2015-Sep-11 22:12:58.154735 BlockchainLMDB::open
2015-Sep-11 22:12:58.155122 BlockchainLMDB::need_resize
2015-Sep-11 22:12:58.155257 DB map size: 1073741824
2015-Sep-11 22:12:58.155391 Space used: 967413760
2015-Sep-11 22:12:58.155522 Space remaining: 106328064
2015-Sep-11 22:12:58.155650 Size threshold: 0
2015-Sep-11 22:12:58.155811 Percent used: 0.9010 Percent threshold: 0.8000
2015-Sep-11 22:12:58.156804 Threshold met (percent-based)
2015-Sep-11 22:12:58.156940 LMDB memory map needs resized, doing that now.
2015-Sep-11 22:12:58.157083 BlockchainLMDB::do_resize
2015-Sep-11 22:12:58.157331 LMDB Mapsize increased. Old: 1024MiB, New: 2048MiB
bitmonerod then silently exits after this, and restarted by supervisor. Nothing else shows up in the logs.
I should have mentioned that my monero deamon is continuously restarted and no longer syncing. This is an excerpt from supervisord.log:
2015-09-07 17:04:44,093 INFO exited: bitmonerod (terminated by SIGSEGV (core dumped); not expected)
2015-09-07 17:04:45,098 INFO spawned: 'bitmonerod' with pid 9719
2015-09-07 17:04:46,114 INFO success: bitmonerod entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-09-07 17:04:48,401 INFO exited: bitmonerod (terminated by SIGSEGV (core dumped); not expected)
2015-09-07 17:04:49,406 INFO spawned: 'bitmonerod' with pid 9726
2015-09-07 17:04:50,426 INFO success: bitmonerod entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-09-07 17:04:52,640 INFO exited: bitmonerod (terminated by SIGSEGV (core dumped); not expected)
Ad infinitum.
I assumed this had something to do with the messages in the bitmonerod (in my first post). Will toy around with the router though when I get a chance...
Are you using a fairly recent build from github? I would try to delete the blockchain data files and try to re-sync.
Also, you may need to hop on #monero-dev or go the the Monero support thread on bitcointalk. I'm not well versed with linux.
I compiled from the source code on GitHub.
I tried deleting the blockchain data. It then re-synced. I'm not sure up to what point but now, a day later, the deamon still exits with the same errors in the logs as above.
Cross-posted this on Bitcointalk...