1
Dhurgan
Re: Upgrade problem going from 2.3.3 to 2.5.10
  • 2019/12/11 21:49

  • Dhurgan

  • Just popping in

  • Posts: 68

  • Since: 2004/2/11


Hacks might be a problem, I have disabled all modules but the System one.
The databases are, as you said, more or less identical, I noticed the change in password size... but figured that could not cause such a stop

At the moment I have made a fresh install of Xoops and is looking to see if I can populate it with the data from the old one in some manner, i can code so importing data from one and moving it over to the other should be ok if it needs some converting, but so far it looks to be ok

It simply wont get past that step in the process, but if there is a protector hack that might block it... then I need to figure that one out



2
Dhurgan
Re: Upgrade problem going from 2.3.3 to 2.5.10
  • 2019/12/9 6:50

  • Dhurgan

  • Just popping in

  • Posts: 68

  • Since: 2004/2/11


That was my plan if there wasn't any ready made difference scripts...
A fresh install it is then... it's always troublesome when there large jumps in versions, especially since everything jumped in the LAMP also :)



3
Dhurgan
Upgrade problem going from 2.3.3 to 2.5.10
  • 2019/12/8 21:52

  • Dhurgan

  • Just popping in

  • Posts: 68

  • Since: 2004/2/11


Hi,
I have a really old xoops 2.3.3 install running under php 5.2.17, MySQL 5.1 on Apache 2.2 on Solaris 11 that I am now trying to move to Ubuntu 18-04 with php 7.2.24, MySQL 5.7.28
I dumped the db from the old and uploaded it into the newver mysql without problems, all data seems to be there, I also moved the old xoops install over and configured it under the local apache and php.
I then followed the upgrade instructions and used the XoopsCore25-2.5.10 package and prepared it in accordance with the instructions and started the upgrade by referencing the upgrade folder on my website. I got to log in as the admin of the site and the upgrade proceeded immediatly to the step 2.4.x to 2.5.0 and presented the message Applied patch upd-2.4.x-to-2.5.0 and a Continue button.

However, pressing that Continue button does nothing... just presents the saem page again.

if I clear the index.php from the path, it's presents the step before as the last done and wants to rerun the 2.4.x to 2.5.0 step, doing that sends us back to the state before...

Checking the error.log it shows the message...
Upgrade required on users table!, referer:
So apparently some step in the upgrade has required a db schema change.

Are those changes possible to get as sql command files from here, all I find is php scripts that does some sql calls that might be doing this, but a simple modify table script would be cool if you have for the changes?

Or maybe this is a known bug, I see more people had trouble with that step before.

/Dhurgan, long time user of a very old xoops :)



4
Dhurgan
Re: PHP Fatal error: Possible integer overflow in...
  • 2007/12/17 22:26

  • Dhurgan

  • Just popping in

  • Posts: 68

  • Since: 2004/2/11


Ok, found the trouble...
One of the twelve CPU's in the system had a bit fualt in bit 2 of its integer calculations... with that CPU off, it works flawlessy again...

The CPU doesnt show any errors during testing, but the fault dissapears completely with that one off.
/Dhurgan ...



5
Dhurgan
Re: PHP Fatal error: Possible integer overflow in...
  • 2007/12/5 7:31

  • Dhurgan

  • Just popping in

  • Posts: 68

  • Since: 2004/2/11


Well, its a twelve CPU system, and none of them has reported any errors...

Basically its PHP code that fails... even the reinstall of it fails at times due to this error...

Its a Sun Enterprise 4500 running Solaris 9 and it reports no faults at all at the moment... has been running fine for five years with patching and reboots at times.

so its probably not XOOPS anyway, its probably somethign in the system
/Dhurgan ...



6
Dhurgan
Re: PHP Fatal error: Possible integer overflow in...
  • 2007/12/4 15:30

  • Dhurgan

  • Just popping in

  • Posts: 68

  • Since: 2004/2/11


memory limit is 128Mb at the moment...
system has 12Gb
but I will check the memory, the system has correctable memory and would only stop if it had multiple bit errors on a byte, it logs all occurences of single ones which it does correct
/Dhurgan ...



7
Dhurgan
Re: PHP Fatal error: Possible integer overflow in...
  • 2007/12/4 15:19

  • Dhurgan

  • Just popping in

  • Posts: 68

  • Since: 2004/2/11


try reloading a few times, suddenly the page is there...
the system itself is pretty secure, but of course, any XOOPS vulnerability might be exposed...

no files has been changed on the server, according to the server, but again, a true hacker would NOT leave such obvious tracks...

thing is, it breaks the page at times, also, with php errors on in xoops, some pages give hundreds of errors regarding the way XOOPS handles variables...

I can turn it on so you can see, the system is broken anyway now...
/Dhurgan ...



8
Dhurgan
PHP Fatal error: Possible integer overflow in...
  • 2007/12/4 13:54

  • Dhurgan

  • Just popping in

  • Posts: 68

  • Since: 2004/2/11


Hi,

I have been running XOOPS for quite sometime now and it has been sometime since I updated since it has been working fine.
Now November 24, no changes made to server, or config or any other part of the system, php suddenly started throwing exceptions when running xoops...

these exceptions sometime give error messages of the following sort...

PHP Fatal error: Possible integer overflow in memory alloc
ation (4 * 1 + 0) in /usr/local/webroot/www.imagine3d.org/html/class/errorhandle
r.php on line 69

Its not always the same file, but its always the memory allocation that faults...

They did not exists before as I can see in logfiles.
I tried repairing the database, and even have upgraded apache and php to latest stable version of their class
(was apache 2.0.52 -> 2.0.61, php 4.1.x -> 4.4.7)
but that hasnt changed it at all, it still throws these errors

What bothers me most is that I cant find anything that has changed on the server, Solaris 9, ES4500

Anyone seen anything like this? At the php site they have seen random events like this, but simply want one to run the latest php, which I did, fault is still there.

Due to these faults, my site shows the page at times, but then other times its just blank or partly shown...

http://www.imagine3d.org

other XOOPS sites I have at same server also faults...

Has anyone had this experience and if so, how did you get around it? I am on a fairly old xoops, (2.0.9.2) I know.

/Dhurgan
/Dhurgan ...



9
Dhurgan
Re: not login in
  • 2007/8/13 11:16

  • Dhurgan

  • Just popping in

  • Posts: 68

  • Since: 2004/2/11


I dont know that tool, but in my case it was my session database that was crashed, if that tool does what its supposed to I guess you dont have the same problem I did.

when you repaired your DB, was it stopped?

I never got the user menu but was thrown directly to the anonymous first page again...

if you use firefox for a browser, you can download the liveheaders addon and check whats going on in the background...
...it might point out something interesting...
/Dhurgan ...



10
Dhurgan
Re: how can I change xoops to be like this simple website
  • 2007/8/13 11:12

  • Dhurgan

  • Just popping in

  • Posts: 68

  • Since: 2004/2/11


Yes its possible, almost anything is possible...

You would need to make a theme, or take one similiar enough to what you need, and then fill it with the blocks you need.

The blocks might be doable with one of the existing tools/modules or custom-made...

Everything is possible, but if your information is this specific, maybe you would be better of just building it yourself with php/mysql/smarty?

It all depends on what you want to be able to do on the pages...
/Dhurgan ...




TopTop
(1) 2 3 4 ... 7 »



Login

Who's Online

188 user(s) are online (105 user(s) are browsing Support Forums)


Members: 0


Guests: 188


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits