Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: chris burnat on January 22, 2004, 01:16:19 AM

Title: 50_turba_upgrade?
Post by: chris burnat on January 22, 2004, 01:16:19 AM

Just installed a box with Vs6.  All is well until last line of the boot:

Jan 22 02:21:48 mail 50turba_upgrade_1.1_to_1.2: DBI->connect(horde) failed: Access denied for user: 'horde@localhost' (Using password: YES) at /etc/e-smith/sql/init/50turba_upgrade_1.1_to_1.2 line 43
Jan 22 02:21:48 mail mysql.init: Loading 50turba_upgrade_1.1_to_1.2 into mysql failed
Jan 22 02:22:02 mail last message repeated 2 times

To be on the safe side, I have re-installed a couple of times, to no avails.  I do not recall seeing this previously.  The box was on the Net, had sync with time server at Deakins Uni.  Can anyone shed some lights?

Many thanks

chris

Title: 50_turba_upgrade?
Post by: Boris on January 22, 2004, 01:51:47 AM

It a known problem (bug). Just search the recent postings (horde password) for workaround.

Title: 50turba_upgrade_1.1_to_1.2
Post by: mrjhb3 on January 29, 2004, 02:39:51 AM

Don't know how many people are still tracking this, but this error is random and I haven't been able to figure out why.  I have loaded my 2 test boxes over 25 times and on some installs I get this error and on others I don't.  The posted fixes don't work as well.
Here is what I have found will fix it temporarily.
Do a /sbin/e-smith/config show horde DbPassword, then go into mysql and type  grant all on horde.* to horde identified by '{password from above command}'; then reboot the server.  You should see that 50turba_upgrade_1.1_to_1.2 will load ok this time.  BUT, the next time you do a /sbin/e-smith/signal-event post-upgrade, this will return the error above and those steps need to be done again.  The above has worked for me everytime I have had the failed error.  Hopefully, this info can help someone else spot how to totally fix this.  This problem was posted in the bugs section, but I think it has been closed with the resolution that was given.  I still see this as a bug.  If anyone else can confirm that the above works for them, the I can see about getting this bug re-opened to be looked at.

Title: 50_turba_upgrade?
Post by: chris burnat on January 29, 2004, 02:28:08 PM

Thanks Boris (correct?).  I was feeling a little in the cold with this one, being pretty new to this technology, and easely baffled...  I will try  your suggestion and let you know if I can manage.  One thing is certain, I am running TWO boxes, both similar M/B and hardware, and BOTH reproduce this bug consistently - 100% of the time.  Loaded around 10 times now from fresh, and a few times as an upgrade from 5.6.  To mention that 5.6 works fine, no errors.  

cheers

christian

PS: I wonder if the distro I have purchased from my local linux store in Sydney is in fact a beta3 upgraded to final version - just a thought. How do I check this ???

Title: more into
Post by: jb on January 29, 2004, 09:22:24 PM

5f9b3f8d62e1f0d1c7034b306758631a  
smeserver-6.0unsupported.iso

do a md5sum on your 6.0 iso file to see if you match the above.  If you do, you have the 6.0 release.

Title: 50_turba_upgrade?
Post by: chris burnat on January 30, 2004, 07:58:51 AM

checksum is:cb8bb2420c59f7a677818b2437fe6e9c
Can you identify this?
Many thanks

Title: 50_turba_upgrade?
Post by: mrjhb3 on January 31, 2004, 04:30:20 AM

Quote from: "burnat"

checksum is:cb8bb2420c59f7a677818b2437fe6e9c
Can you identify this?
Many thanks

I can't identify that checksum.  I ran md5sum on my ISO after I found someone else who had posted their checksum.  Mine matched theirs so I figured I had a good ISO.  I haven't seen anywhere on contribs.org that shows what the checksum of the ISO they have that they are making available for download.

JB

Title: 50_turba_upgrade?
Post by: chris burnat on February 04, 2004, 12:35:50 AM

All very strange...

1) Using a distribution with checksum cb8bb2420c59f7a677818b2437fe6e9c on a Gigabyte M/B 2.4Ghz, the problem can be repeated times and times again.

2) Install on an other box (180MMX dual processor / 6 year old), with the same distro (checksum cb8bb2420c59f7a677818b2437fe6e9c)., no problem, did it a couple of times to be sure.  No error whatsoever!

3) Download ISO from a link found on this site via Australian mirror.  Published checksum of ISO is : 5f9b3f8d62e1f0d1c7034b30675863a1.  Burn CD and get checksum e2f2c40b6c7b0feab484c6cde8d6f74b.  Install on the the new Gygabyte M/B.  Result:  No error!

Problem appears solved for the time being, I will use new CD build from ISO rather than the one I bought at my linux shop.
Still, its very odd...  Two variables, M/B and distro. The above may provide some clues for someone experienced in this type of challenges?