Temat: minidlna - błędy w logach
Witam.
Świeża instalacja gargoyle-1.9.1.1-ar71xx na ZyXEL NBG6716. Mój config minidlna poniżej.
config minidlna 'config'
option enabled '1'
option port '8200'
option interface 'br-lan'
option friendly_name 'OpenWrt DLNA Server'
option inotify '1'
option enable_tivo '0'
option strict_dlna '0'
option notify_interval '900'
option serial '12345678'
option model_number '1'
option root_container '.'
option album_art_names 'Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg/AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg/Folder.jpg/folder.jpg/Thumb.jpg/thumb.jpg'
list media_dir '/tmp/usb_mount/000aa4e4-02/dlna'
option db_dir '/tmp/usb_mount/000aa4e4-02/dlna/.config'
option log_dir '/tmp/usb_mount/000aa4e4-02/dlna/.config'Niby działa, choć ze 2 razy miałem problem z połączeniem. Po restarcie było ok i teraz jest ok. Jednak błędy w logach są cały czas. Pozostałe urządzenia korzystające z dlna podłączone są do routera po kablu utp. Wycinek z logów minidlna.
[2016/11/06 11:13:07] minidlna.c:154: warn: received signal 15, good-bye
[2016/11/06 11:13:29] minidlna.c:1030: warn: Starting MiniDLNA version 1.1.5.
[2016/11/06 11:13:29] minidlna.c:1070: warn: HTTP listening on port 8200
[2016/11/06 11:14:40] minidlna.c:1030: warn: Starting MiniDLNA version 1.1.5.
[2016/11/06 11:14:40] minidlna.c:1070: warn: HTTP listening on port 8200
[2016/11/06 11:16:07] getifaddr.c:109: error: Network interface br-lan not found
[2016/11/06 11:16:07] getifaddr.c:109: error: Network interface br-lan not found
[2016/11/06 11:16:08] getifaddr.c:109: error: Network interface br-lan not found
[2016/11/06 11:16:09] minidlna.c:154: warn: received signal 15, good-bye
[2016/11/06 11:16:30] minidlna.c:1030: warn: Starting MiniDLNA version 1.1.5.
[2016/11/06 11:16:30] minidlna.c:1070: warn: HTTP listening on port 8200
[2016/11/06 11:17:42] minidlna.c:1030: warn: Starting MiniDLNA version 1.1.5.
[2016/11/06 11:17:42] minidlna.c:1070: warn: HTTP listening on port 8200
[2016/11/06 11:23:50] upnphttp.c:1012: warn: /favicon.ico not found, responding ERROR 404
[2016/11/06 11:28:42] upnphttp.c:1012: warn: /favicon.ico not found, responding ERROR 404
[2016/11/06 11:46:05] upnphttp.c:1012: warn: /favicon.ico not found, responding ERROR 404
[2016/11/06 11:46:31] upnphttp.c:1052: warn: HTTP Connection closed unexpectedly
[2016/11/06 11:46:31] upnphttp.c:1052: warn: HTTP Connection closed unexpectedly
[2016/11/06 11:46:31] upnphttp.c:1052: warn: HTTP Connection closed unexpectedly
[2016/11/06 11:46:31] upnpevents.c:362: warn: upnp_event_send: send(): Connection refused
[2016/11/06 11:46:31] upnpevents.c:362: warn: upnp_event_send: send(): Connection refused
[2016/11/06 11:46:31] upnpevents.c:362: warn: upnp_event_send: send(): Connection refused
[2016/11/06 11:50:03] upnphttp.c:1052: warn: HTTP Connection closed unexpectedly
[2016/11/06 11:50:03] upnphttp.c:1052: warn: HTTP Connection closed unexpectedly
[2016/11/06 11:50:03] upnphttp.c:1052: warn: HTTP Connection closed unexpectedly
[2016/11/06 11:50:26] upnphttp.c:1012: warn: /favicon.ico not found, responding ERROR 404
[2016/11/06 11:50:40] upnphttp.c:1052: warn: HTTP Connection closed unexpectedly
[2016/11/06 11:51:48] upnphttp.c:1012: warn: /favicon.ico not found, responding ERROR 404
[2016/11/06 11:52:32] upnphttp.c:1052: warn: HTTP Connection closed unexpectedly
[2016/11/06 12:05:46] upnphttp.c:1012: warn: /favicon.ico not found, responding ERROR 404
[2016/11/06 12:14:31] upnphttp.c:1012: warn: /favicon.ico not found, responding ERROR 404
[2016/11/06 12:14:41] upnphttp.c:1052: warn: HTTP Connection closed unexpectedly
[2016/11/06 12:24:15] upnphttp.c:1012: warn: /favicon.ico not found, responding ERROR 404
[2016/11/06 12:25:03] upnpevents.c:362: warn: upnp_event_send: send(): Connection refused
[2016/11/06 12:25:03] upnpevents.c:362: warn: upnp_event_send: send(): Connection refused
[2016/11/06 12:25:03] upnpevents.c:362: warn: upnp_event_send: send(): Connection refused
[2016/11/06 12:27:22] upnphttp.c:1012: warn: /favicon.ico not found, responding ERROR 404
[2016/11/06 12:28:27] upnpevents.c:362: warn: upnp_event_send: send(): No route to host
[2016/11/06 12:28:27] upnpevents.c:362: warn: upnp_event_send: send(): No route to hostDruga sprawa mniej istotna ale jedna ciekawi. Edytowałem plik /www/js/minidlna.js w którym zmieniłem _minidlna na .config
Następnie restart routera. Po czym w GUI --> DLNA jak robię zapisz to i tak nie wiem skąd tworzy mi pliki _minidlna pomimo że w minidlna.js jest już .config
W wersji Gargoyle AA tak robiłem nie było problemów. Natomiast w bieżącej wersji Gargoyle CC radze sobie tak że ręcznie edytuję /etc/config/minidlna wpisując tam
option db_dir '/tmp/usb_mount/000aa4e4-02/dlna/.config'
option log_dir '/tmp/usb_mount/000aa4e4-02/dlna/.config'I nie zapisując zmian w GUI --> DLNA
TP-Link TL-WDR4300 Mod, CPU 700MHz, Flash 16 MB, Gargoyle 1.5.11.4, extroot + dysk zewnętrzny Samsung (S2), kamerka MS LifeCam HD-5000
TP-Link TL-WR1043ND Mod, RAM 64 MB, chłodzenie pasywne, Gargoyle 1.5.10.14, extroot, kamerka Logitech HD Webcam C270
TP-Link TL-WR1043ND Mod, RAM 64 MB, chłodzenie pasywne, Gargoyle 1.5.10.14, extroot, kamerka Logitech HD Webcam C270