vicidial.org

I decided to open a new thread on these issues.

We now used three different servers using the 3.0.8 64bit disc on all these servers. We used three different options to see if the problems are replicated on all the installs.

Server 1

Update OS - N
Update SVN - N
Turn firewall off - Y
Database - Y
Web - N
Telephony - N
Large Database Support - Y

Then I simply hit enter on all the defaults. (MySql username = cron Password = 1234)

Result: The database schema shows in system settings. MySql -p with password 1234 gives a wrong password error. When I leave the password empty I gain access to MySql.

Server 2

Update OS - N
Update SVN - Y
Turn firewall off - Y
Database - Y
Web - N
Telephony - N
Large Database Support - Y

Then I simply hit enter on all the defaults. (MySql username = cron Password = 1234)

Result: This installation does not download the SVN, it installs the SVN version that is on the disc. The database schema does not show in system settings. MySql -p with password 1234 gives a wrong password error. When I leave the password empty I gain access to MySql.

Server 3

Update OS - Y
Update SVN - Y
Turn firewall off - Y
Database - Y
Web - N
Telephony - N
Large Database Support - Y

Then I simply hit enter on all the defaults. (MySql username = cron Password = 1234)

Result: This installation does download the SVN. The database schema does not show in system settings. MySql -p with password 1234 gives a wrong password error. When I leave the password empty I gain access to MySql.[/u]

MySql -p with password 1234

will never work. what this is asking the system to do is "log in to mysql as the present user (root!) with a password of 1234". But root has no password. Cron, on the other hand, has a passwod of 1234. So:

Code: Select all

mysql -u cron -p1234

will work much better.

Thanks William! Now I am only left with one "issue"

have you been able to try other scenarios to verify "OSUpdate"="Y" is the only way to get your installations to download SVN?

(not just a fluke?)

Use SVN will use the SVN Code on the disk. This has nothing to do with downloading a more current SVN.

OS Update will cause it to update the operating system, AND connect out to the internet and update the SVN Code on the disk to the current.

Nothing will make it update the SVN Code unless you select "OS Update".

I will see if I can duplicate the schema issue you are describing.

would it not be more "clear" to remove the SVN Update if OS update is "N"? (thus removing the misunderstanding?)

or change the phrase to "SVN Install" instead of "SVN Update"? (unless he copied that wrong ... i don't have one in front of me.

Hi

The SVN update is not an issue for me - I just mentioned it to illustrate the different methods I used to install. Only the database schema is the issue. Thanks a lot for the help! I have downloaded several discs and used 5 different servers now just in case but keep getting the same result.

I had the same problem;

What I saw in apache logs was some queries being made with some rows that didn't exists in database

The solution for me was:

mysql

use asterisk
\. /usr/src/astguiclient/trunk/extras/upgrade_2.4.sql

I am soooo happy to see other people also get this! I thought I am a total moron by now!

ERROR 1091 (42000) at line 587 in file: './upgrade_2.4.sql': Can't DROP 'uniqueid'; check that column/key exists

Is this the same error you got?

that is the error that you receive when you run to update mysql database from the sql?

I din't looked exacly but that error is there beceause it can't find that column in your database.

Anyway after I run that upgrade the system is working.

The phrase "Update SVN" is never presented as a wizard option. It only every says "Use SVN".

If you want to update things select Update. It's that simple. Use SVN only uses the SVN code preasent on the disk.

As far as the DB Schema not updating that is confirmed. I am not sure why that is happening, but the short-fix is to run this command as root on the database:

/usr/bin/mysql asterisk --execute="\. /usr/src/astguiclient/trunk/extras/upgrade_2.4.sql"

An alternative would be doing what Iulianm suggested, which runs the same sql file just in a different method.

I am trying to figure out why the schema is not updating completely. It partially updates but not fully.

Hi Kumba

Thank you very much for the feedback. Yes, apologies, when I reported the issue I wasn't in front of a server so I got the wording messed up a bit.

Hi Kumba

Will there be a 3.0.9 release when this bug is fixed or will it be fixed within 3.0.8?