Getting an error....

[Pinholic]

When I run the autopatcher script I get the following error: kurt@Office:/var/www$ cd /var/www/nZEDbetter/misc/testing/DB_scripts kurt@Office:/var/www/nZEDbetter/misc/testing/DB_scripts$ php autopatcher.php true PHP Warning: mysqli::mysqli(): Headers and client library minor version mismatch. Headers:50534 Library:50614 in /var/www/nZEDbetter/www/lib/framework/db.php on line 27 PHP Stack trace: PHP 1. {main}() /var/www/nZEDbetter/misc/testing/DB_scripts/autopatcher.php:0 PHP 2. DB->DB() /var/www/nZEDbetter/misc/testing/DB_scripts/autopatcher.php:7 PHP 3. mysqli->mysqli() /var/www/nZEDbetter/www/lib/framework/db.php:27 Already up-to-date. Nothing to remove from /var/www/nZEDbetter/www/lib/smarty/templates_c/ Patching database - nzedbetter PHP Warning: mysqli::mysqli(): Headers and client library minor version mismatch. Headers:50534 Library:50614 in /var/www/nZEDbetter/www/lib/framework/db.php on line 27 PHP Stack trace: PHP 1. {main}() /var/www/nZEDbetter/misc/testing/DB_scripts/patchmysql.php:0 PHP 2. Sites->get() /var/www/nZEDbetter/misc/testing/DB_scripts/patchmysql.php:72 PHP 3. DB->DB() /var/www/nZEDbetter/www/lib/site.php:66 PHP 4. mysqli->mysqli() /var/www/nZEDbetter/www/lib/framework/db.php:27 ERROR: Have you changed the path to the patches folder, or do you have the right permissions?

Have done chmod -R 0777 nZEDbetter on folder so permissions are ok? Also when I run start.php im seeing a lot of Headers and client library minor version mismatch. Headers:50534 Library:50614 errors in all panes.

What am i doing wrong?

[KurzonDax]

First item is autopatcher - I haven't actually updated that script (largely because I never really used it). I'll take a look at it this weekend and see what needs to be done to make it work correctly. For now, I'm not making any immediate changes to the DB schema, so you won't need to worry about that. If you want to update the actual scripts, pages, etc., just do a git pull and you should be good.

From your /var/www/nZEDbetter directory, you should be able to just type:

sudo git pull

This should work provided you haven't made any changes to the core files yet. If you have made changes, the pull will fail, in which case the easiest solution (for now) is to git clone in to a temp directory somewhere and then manually copy the files over the /var/www/nZEDbetter directory.

As for the Header/client mismatch errors, you didn't do anything wrong. I did. You'll probably see them when viewing the site in a browser also. It's a pretty easy fix though. Edit /etc/php5/cli/php.ini and search for the following line:

error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT

and change it to:

error_reporting = E_ERROR

You'll need to make the same change in /etc/php5/apache2/php.ini. Also, remember, you have to edit these files using sudo. I've got to update the setup script and the documentation on this. This one is due to me being an idiot every once in a while. LOL Let me know if this worked for you.

[Pinholic]

Thanks mate, that sorted it. Noticed now though I'm seeing Error unexpected response: Order of fields in overview database Attempting to reconnect to usenet This is in the top right pane of monitor window. Doesn't seem to be affecting the process though?

[KurzonDax]

This is usually because the usenet service provider responded to a request with something weird. I'm guessing it's happening when we send the request for the headers, though I haven't actually seen that error message before. Out of curiosity, who do you use for your newsgroups provider? Does it appear constantly, or does it only happen every once in a while? If it's not happening all the time, and your parts, binaries, and collections tables are getting filled, it's probably not a huge deal. If it is happening all the time, I can see if I can add some code to try and log some information about it.

In my previous response, I said I wasn't going to make any changes to the DB schema any time soon. Well, as it turns out, I discovered a couple of things tonight that are going to require DB changes:

1. I mistakenly left a couple of indexes in the parts table from some testing I was doing. They're definitely not needed, and are causing the index size to be significantly larger than it needs to be. This also impacts performance because we're updating unnecessary indexes every time parts are added.
2. Nevermind on this one. I just found a major flaw in my plan. Stay tuned for more details.

[Pinholic]

I use newsleecher which is a reseller of astraweb. The error is there all the time :-( but yes the tables are still getting filled. Will stay tuned :-)

[KurzonDax]

Interesting. I'll see where the best place to add some logging code would be this weekend and update the repo.

[KurzonDax]

btw, I just found a nasty little bug I introduced with a commit a couple of days ago. If no releases are getting created, let me know. It's an easy fix.

[Pinholic]

Am doing a fresh install later on a faster machine so I will let you know if there's a problem with releases being created. Another quick question, is it ok to import the PreDB dump from the nzedb website?

[KurzonDax]

If the preDB table hasn't been populated with anything yet, then yes, it's perfectly fine to import it. Once you've started the tmux scripts the first time though, you may run in to an issue due to duplicate keys. I've had fixed the problem in my own version of the preDB files from nZEDb, but then virtual machine I was using at the time had some major disk corruption and I lost it. I'll fix them again soon and upload my own version to a repo.

[KurzonDax]

By the way, were you ever able to get your MusicBrainz replica going?

[Pinholic]

No I'm afraid I never got the users sorted out, even after following your instructions to the letter. Am planning to give it another go incase I messed up somewhere along the way. Looking forward to a fixed PreDB dump from you. In nzedb there was a PreDB tab on the homepage, don't see this in nzedbetter or am I blind?

[KurzonDax]

The preDB menu item is just disabled. In the Admin section, go to the Content tab, and select Menu Items. On the page that comes up, click on the PreDB name. On the next page that comes up, take out the -1 in the Evaluate field (just make the field blank) and save. PreDB will show up on the main site menu again.

I'm going to rebuild my MusicBrainz replica again, so I'll walk through my instructions and figure out what needs fixed. Probably won't happen this weekend. Maybe next week if my day job isn't so crazy.

Also, I definitely found a much better way to dump incomplete collections during the purge process. I'm letting it run through the weekend and will see how it does, but it should make it much easier to index more groups and not require quite so much RAM.