barbergeek

Enable GPU acceleration if you can, even the built-in Intel GPU if you have a Core i-something. Makes a HUGE difference.

Good day, all. I have a new Windows 8.1 box that I've built that won't see my 6.0.1 UnRAID server. I can't ping it, can't connect to shares, can't connect to the GUI. It's as if it doesn't exist. Ping reports "Destination host unreachable" and it never shows up in the arp table. Tried putty to connect via ssh. Putty reports "Network error: Connection timed out" Everything else on the network seems fine. I can ping my router, external sites, other devices on the network. I can surf, no apparent issues. Other PCs and macs in the house can connect to the UnRAID server just fine, and I can see them from the new 8.1 box. MB in the pc is a bit old. It's an Asus P6T Deluxe V2, with the current BIOS. Has 2 Marvell 88E8055 GbE controllers. No difference if I use either one. One other odd thing though. I can't ping the 8.1 box, even with the firewall turned off. I'm puzzled. Any ideas? I did check through the forum and look at all the other relevant posts. No resolution. Thanks! Scott

You'd think I'd remember that by now... That was it. Sorry for the false alarm. I think I'm good now. Thanks again. Very much appreciate all your support!

Ok, let it run all night and got much, much further. The ui fails now with this error: Caught exception in MusicBrainz::Server::Controller::Root->begin "08006 DBI connect('dbname=musicbrainz_db','musicbrainz',...) failed: FATAL: could not open relation mapping file "global/pg_filenode.map": No such file or directory at lib/MusicBrainz/Server/Connector.pm line 42. If I look in /data/main, it's empty except for the global and pg_xlog directories. The database files that were there seem to have disappeared. Hmm, I think mover may be killing me... let me look into that.

Standby... tried again and made sure everything was really cleaned out this time. May be making it further...

Well, here's maybe one thing... In the /root directory in the docker, there's a supervisord.conf. The command line for postgres is this: command=/usr/lib/postgresql/9.4/bin/postgres -D /data/main -c config_file=/data/main/postgresql.conf I did notice that the config_file appears to be at /data/postgresql.conf, not /data/main/postgresql.conf, unless it puts it there later and I just haven't gotten there yet. ??

Ok, deleted /mnt/cache/apps/musicbrainz and /mnt/cache/data/musicbrainz and started a new build. Import files are downloading but postgresql is definitely not running. Same error as before. Tried to spawn postgres but immediately exited with error status 2. Tried a few times and then gave up. I looked around for another log to try to find the error, but couldn't locate anything that looked relevant. Can you point me to something? Thanks again! Scott

Ok, I'll give that a shot. Here's the rest of the log though, after it finished downloading the import /data/import / mbdump-cdstubs.tar.bz2: OK mbdump-cover-art-archive.tar.bz2: OK mbdump-derived.tar.bz2: OK mbdump-documentation.tar.bz2: FAILED open or read mbdump-edit.tar.bz2: FAILED open or read md5sum: mbdump-documentation.tar.bz2: No such file or directory md5sum: mbdump-edit.tar.bz2: No such file or directory mbdump-editor.tar.bz2: OK mbdump-stats.tar.bz2: OK mbdump-wikidocs.tar.bz2: OK mbdump.tar.bz2: OK md5sum: WARNING: 2 listed files could not be read Failed query: 'SELECT version();' () 08006 DBI connect('dbname=template1','postgres',...) failed: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? at /opt/musicbrainz/admin/../lib/MusicBrainz/Server/Connector.pm line 42. at /opt/musicbrainz/admin/../lib/Sql.pm line 463. Sql::catch {...} ('08006 DBI connect(\'dbname=template1\',\'postgres\',...) fail...') called at /usr/local/share/perl/5.18.2/Try/Tiny.pm line 104 Try::Tiny::try('CODE(0x212fd38)', 'Try::Tiny::Catch=REF(0x2142090)', 'Try::Tiny::Finally=REF(0x906188)') called at /opt/musicbrainz/admin/../lib/Sql.pm line 469 Sql::_select_list('Sql=HASH(0x1e48998)', 'SELECT version();', 'ARRAY(0x205a960)', 'arrayref', 'CODE(0x2069688)') called at /opt/musicbrainz/admin/../lib/Sql.pm line 488 Sql::select_list_of_lists('Sql=HASH(0x1e48998)', 'SELECT version();') called at /opt/musicbrainz/admin/../lib/Sql.pm line 419 Sql::select_single_column_array('Sql=HASH(0x1e48998)', 'SELECT version();') called at /opt/musicbrainz/admin/../lib/Sql.pm line 434 Sql::select_single_value('Sql=HASH(0x1e48998)', 'SELECT version();') called at ./admin/InitDb.pl line 74 main::RequireMinimumPostgreSQLVersion() called at ./admin/InitDb.pl line 529 08006 DBI connect('dbname=template1','postgres',...) failed: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? at /opt/musicbrainz/admin/../lib/MusicBrainz/Server/Connector.pm line 42. at /opt/musicbrainz/admin/../lib/Sql.pm line 465. Sql::catch {...} ('08006 DBI connect(\'dbname=template1\',\'postgres\',...) fail...') called at /usr/local/share/perl/5.18.2/Try/Tiny.pm line 104 Try::Tiny::try('CODE(0x212fd38)', 'Try::Tiny::Catch=REF(0x2142090)', 'Try::Tiny::Finally=REF(0x906188)') called at /opt/musicbrainz/admin/../lib/Sql.pm line 469 Sql::_select_list('Sql=HASH(0x1e48998)', 'SELECT version();', 'ARRAY(0x205a960)', 'arrayref', 'CODE(0x2069688)') called at /opt/musicbrainz/admin/../lib/Sql.pm line 488 Sql::select_list_of_lists('Sql=HASH(0x1e48998)', 'SELECT version();') called at /opt/musicbrainz/admin/../lib/Sql.pm line 419 Sql::select_single_column_array('Sql=HASH(0x1e48998)', 'SELECT version();') called at /opt/musicbrainz/admin/../lib/Sql.pm line 434 Sql::select_single_value('Sql=HASH(0x1e48998)', 'SELECT version();') called at ./admin/InitDb.pl line 74 main::RequireMinimumPostgreSQLVersion() called at ./admin/InitDb.pl line 529 IMPORT IS COMPLETE, MOVING TO NEXT PHASE *** Running /etc/my_init.d/004-import-databases--and-or-run-everything.sh... *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 112 Jun 17 22:25:51 0ae6ac8db702 syslog-ng[117]: syslog-ng starting up; version='3.5.3' And if I go to port 5000, I get this error: caught exception in MusicBrainz::Server::Controller::Root->begin "08006 DBI connect('dbname=musicbrainz_db','musicbrainz',...) failed: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? at lib/MusicBrainz/Server/Connector.pm line 42. [plus about 500 additional lines of error...] I'll try a complete clean rebuild. Thanks!

I've been trying to get this to run and have been having numerous problems. I'm trying a fresh install and it seems that the postgresql server won't start. I have config and data pointing to separate directories on my cache drive, so I've solved that problem at least. Just can't seem to get it running "out of the box". Anyone else having similar problems? Here's the docker log: ?*** Running /etc/my_init.d/001-fix-the-time.sh... Current default time zone: 'America/New_York' Local time is now: Wed Jun 17 21:16:12 EDT 2015. Universal Time is now: Thu Jun 18 01:16:12 UTC 2015. *** Running /etc/my_init.d/002-configure-DBDefs.sh... DBDefs is in your config folder, may need editing *** Running /etc/my_init.d/003-postgres-initialise.sh... The files belonging to this database system will be owned by user "postgres". This user must also own the server process. initdb: directory "/data/main" exists but is not empty If you want to create a new database system, either remove or empty the directory "/data/main" or run initdb with an argument other than "/data/main". The database cluster will be initialized with locale "en_US.UTF-8". The default database encoding has accordingly been set to "UTF8". The default text search configuration will be set to "english". Data page checksums are disabled. 2015-06-17 21:16:19,134 CRIT Supervisor running as root (no user in config file) 2015-06-17 21:16:19,148 INFO supervisord started with pid 38 2015-06-17 21:16:20,151 INFO spawned: 'redis-server' with pid 42 2015-06-17 21:16:20,154 INFO spawned: 'postgres' with pid 43 2015-06-17 21:16:20,166 INFO exited: postgres (exit status 2; not expected) 2015-06-17 21:16:21,167 INFO success: redis-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-06-17 21:16:21,169 INFO spawned: 'postgres' with pid 46 2015-06-17 21:16:21,185 INFO exited: postgres (exit status 2; not expected) 2015-06-17 21:16:23,188 INFO spawned: 'postgres' with pid 47 2015-06-17 21:16:23,202 INFO exited: postgres (exit status 2; not expected) 2015-06-17 21:16:26,207 INFO spawned: 'postgres' with pid 48 2015-06-17 21:16:26,223 INFO exited: postgres (exit status 2; not expected) 2015-06-17 21:16:27,224 INFO gave up: postgres entered FATAL state, too many start retries too quickly BEGINNING INITIAL DATABASE IMPORT ROUTINE, THIS COULD TAKE SEVERAL HOURS AND THE DOCKER MAY LOOK UNRESPONSIVE DO NOT STOP DOCKER UNTIL IT IS COMPLETED

I hade the same problem and was suspicious that it was miscalculating the temperature threshold. I changed the setting from C to F and the erroneous messages went away. Must be a small bug somewhere as I'd never touched that before, but happy as a clam now.

I have to concur. Working perfectly for me.

I installed the Dynamix v6 system stats plugin and it was quite informative as to what's really going on with the memory. Might want to consider that as part of the standard install. No memory leak evident, definitely using lots of cache though, as it should, my apologies for the confusion. I was occasionally still having difficulty getting to the GUI, but then I noticed it was only on my iPad. I cleared cache and have been unable to reproduce. Odd. I will monitor and opena new thread if I see it pop up again. Thanks everyone for helping clarify.

I guess I would add that if this really is the case, the system stats on the dashboard are pretty misleading (and I don't consider myself at least a total noob ) and it would be helpful to break those stats down a bit into maybe used, cached, and available, or something such. If the GUI continues to die on me, I'll try to debug further. Thanks for the clarification. We'll see what happens.

Well, I am definitely losing access to the UI after about 24 hours or so. I will let everything run for a while and see what free -m reports. Definitely different behavior in b12 than what I had in b10, as it was running pretty great.

Have a new problem that showed up with b12. There seems to be a continuous memory leak that eventually eats the entire available memory pool. I thought it was one of the Docker containers, but Docker is stopped and memory usage, according to the system status, continues to go down. Eventually it gets to 98% and then I lose access to the UI. After rebooting and watching it go up for several hours, I stopped and restarted the array and it went back down to about 10%. It's been sitting (without Docker running) for about 3 hours and it's up to 19%. I have a pretty stock b12 build, with only dlandon's powerdown v2.13 plugin installed. I have been watching htop too and it's gone in that same time from 252 to 454, which, given the 16GB I have installed isn't much, but eventually it gets yellow bars all the way across and a number up close to the 16 gig. Anyone else seeing this or suggestions to help debug? Thanks!

Changing file format does not preserve parity. You need to rebuilt parity after changing a disk file format. Stop the check and rebuild your parity. Will do. Glad I didn't lose a drive in that time. We might want to add a note about that on the disk config page. Thanks!

Upgraded to Beta 12 last night and that seemed to go fine. Started a parity check this morning and after finishing 11%, it's found 32+ million errors. And counting... I did migrate all my drives to xfs last month (one by one) so maybe I should have rebuilt parity after that, but I would have thought the normal parity processing would have caught that. Not sure there's really a problem or not, just reporting an odd occurrence. Anyone else see this?