Hey all,
Was really excited to see this product updated for NAS and linux. I’m a sys admin by day so thought this would be a walk in the park.
The install was a breeze. I didn’t know it was headless at first so poked around for a status page but then realized it only asked for port 1900 to open and that is for device discovery.
First problem was the remote was locked on my pc. Uninstall reinstall didn’t help. Finally figured clearing my cache and data would fix it. Got it pointed to my nas and could get in.
Next thing is I assumed incorrectly that it gave user access to the file system. It let me navigate all around and I gave it top level access to my files. Well nothing synced and I gave the permissions and nothing synced. I tried to additional give a specific folder up and nothing came in. So I removed all folders and tried again. Sync started but stopped 80% of the way with no status. I had seen a place to view logs but couldn’t remember where and decided to sleep on it and let it process.
In the morning still stuck there. So I restarted the package on the NAS and there are some albums.
Now between switching between menus the loading takes forever. Also sometimes it tells me I’m on the wrong wifi network. My NAS is hard wired to my network. Also I have a newer router so speeds aren’t an issue. Haven’t really tried to play anything yet but not super impressed. This is definitely the setup I’d like. I used Audirvana some last year and didn’t like that it wouldn’t run as a service so a headless NAS version would be perfect.
Am I do things wrong here? Do other people have the same problems?
Investigate the log files. When you go to settings > account, there is an ‘open log file’ button in the remote app.
If you want to switch from Audirvana installation between your PC or your NAS, you have to disconnect in the same settings page first and then log on to the other instance running.
Seems to be this -
2024-08-11 01:54:58.103 [info]: Local Library Sync: Files synchronization: Stopping monitoring of subfolders of /volume1/media/torrents
2024-08-11 01:54:58.103 [info]: Local Library Sync: Files synchronization: Only 8191 folders are watched
2024-08-11 01:54:58.103 [info]: Local Library Sync: Files synchronization: Please increase the fs.inotify.max_user_watches value in /etc/sysctl.conf
I guess that makes me wonder if I can add folders for a one time scan rather than having them being watched. I have a huge folder of mixed media including video files that has music in between.
Any recursive permission issues seems to hang the software. Fixing each by hand.
Had one folder owned my 911 because they were auto extracted, scanning again. Had to increase my somaxconn and max_user_watches again. Just put a zero at the end so they are 653500 and a bit less for user watches. Seems to me syncing and will be taking awhile.
Think this would be hard for a less technical person with a NAS.
Seems like it crashed in processing. File with non English characters even though it processed some fine before that by the same artist.
Good thing is most of my library seems to be there.
Library Sync: Not synching unreadable file /volume1/media/torrents/毛ä¸æ˜“ - 平凡的一天 (2018)/CD 2 Instrumental/平凡的一天 CD2.cue
2024-08-11 15:33:01.915 [error]: Remote: event websocket lost with error: Connection reset by peer
2024-08-11 15:38:25.426 [error]: Remote: event websocket lost with error: Connection reset by peer
2024-08-11 15:45:00.828 [error]: Remote: event websocket lost with error: Connection reset by peer
2024-08-11 15:47:46.111 [error]: Remote: event websocket lost with error: Connection reset by peer
I think I was hasty. It seems to be processing more syncs without a status in library or info in the logs because it hit some FLACs at the wrong samplerate so I’ll let it do it’s thing. Listening to some audio and it sounds nice.
And it seems to crash often. Had high pitch noise when up sampling was on so turned that off and playback randomly stops about every four minutes. Here are logs
============= Previous crash log =============
2024-08-11 20:38:48.459 [critical]: Audirvana Origin x86_64 2.5.13.2 crash log
2024-08-11 20:38:48.459 [critical]: Date: 2024-8-12 0:34:53
2024-08-11 20:38:48.460 [critical]:
2024-08-11 20:38:48.460 [critical]: Signal: SIGSEGV
2024-08-11 20:38:48.460 [critical]:
2024-08-11 20:38:48.460 [critical]: /var/packages/audirvana-origin/target/audirvanaOrigin(+0xb9437c)[0x55e03a42337c]
2024-08-11 20:38:48.460 [critical]: /lib64/libc.so.6(+0x3b650)[0x7f0860dd1650]
2024-08-11 20:38:48.460 [critical]: /lib64/libstdc++.so.6(_ZNSt6thread4joinEv+0x8)[0x7f086111a7dc]
2024-08-11 20:38:48.461 [critical]: /var/packages/audirvana-origin/target/audirvanaOrigin(+0x2ed9d5)[0x55e039b7c9d5]
2024-08-11 20:38:48.461 [critical]: /var/packages/audirvana-origin/target/audirvanaOrigin(+0x2e3ac2)[0x55e039b72ac2]
2024-08-11 20:38:48.461 [critical]: /var/packages/audirvana-origin/target/audirvanaOrigin(+0x2f8bfb)[0x55e039b87bfb]
2024-08-11 20:38:48.461 [critical]: /var/packages/audirvana-origin/target/audirvanaOrigin(+0xb924c5)[0x55e03a4214c5]
2024-08-11 20:38:48.461 [critical]: /lib64/libc.so.6(+0x27177)[0x7f0860dbd177]
2024-08-11 20:38:48.461 [critical]: /lib64/libc.so.6(__libc_start_main+0x85)[0x7f0860dbd235]
2024-08-11 20:38:48.461 [critical]: /var/packages/audirvana-origin/target/audirvanaOrigin(+0x144ed5)[0x55e0399d3ed5]
2024-08-11 20:38:48.462 [critical]:
2024-08-11 20:38:48.462 [critical]:
2024-08-11 20:38:48.462 [critical]: Fault location: 0x55E03CE6D740
2024-08-11 20:38:48.462 [critical]: ============= Linux system info =============
2024-08-11 20:38:48.462 [critical]: Linux version 4.4.302+ (root@build7) (gcc version 12.2.0 (GCC) ) #69057 SMP Fri Jan 12 17:02:59 CST 2024
2024-08-11 20:38:48.463 [critical]: ============= End of previous crash log =============
Hi @wcbutler,
Can you send us your whole log file at support@audirvana.com so we can take a look a this?
1 Like
