 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 3/15/21 11:11 AM, Chris Cason wrote:
> On 16/03/2021 01:24, Ash Holsenback wrote:
>> On 3/15/21 10:00 AM, Chris Cason wrote:
>>> It will take some time to audit all the PHP code for side-effects as
>>> we've gone from PHP5 to PHP7 (plus all the database calls have to be
>>> changed as the mysql driver was dropped in favor of mysqli in PHP7).
>>
>> i knew there would be some pain there... i suppose that's why i'm not
>> getting any response from wiki yet.
>
> That's a whole different kettle of fish, unfortunately. The wiki, texlib
> and a few other things run in FreeBSD jails (an OS/process abstraction)
> that have their own completely separate set of files (basically the
> entire operating system). While I technically could try running them
> as-is (iffy as we've gone from 32 to 64-bitOS) it's certain that there
> would be a bit of mucking around. If I decide to upgrade them to the
> latest tools then all the PHP code in there has to be audited as well.
last time i touched wikidocgen i was running php7 on my machine so i
have /some/ confidence, however i've not kept up with mediawiki changes
so i don't know what's in store for that... i'm most fearful of table
name changes. didn't that bite us in the ass last time we upgraded?
we /do/ have a most recent sql dump correct? i haven't ran a mediawiki
on my machine in a while. do you think there's some value in seeing if i
can get that running to see if we can even get it to import?
> Realistically, for the wiki, unless it's possible to force it to run
> with the old php and apache binaries, we'd have no choice but to upgrade
> the entire mediawiki codebase to something current as it's way to big to
> manually audit/change each place the database is used.
i would be surprised if the former... i /think/ we both know where this
is going
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 16/03/2021 04:04, Ash Holsenback wrote:
> On 3/15/21 11:11 AM, Chris Cason wrote:
> last time i touched wikidocgen i was running php7 on my machine so i
> have /some/ confidence, however i've not kept up with mediawiki changes
> so i don't know what's in store for that... i'm most fearful of table
> name changes. didn't that bite us in the ass last time we upgraded?
Your memory is likely better than mine, so perhaps there were. I hope
there'd be some sort of upgrade script if so.
> we /do/ have a most recent sql dump correct?
We have a backup of the DB (not a dump specifically, just the physical
DB directory). While I have yet to bring up mysql I don't anticipate
problems.
> on my machine in a while. do you think there's some value in seeing if i
> can get that running to see if we can even get it to import?
Yes, that would be great. I'll get the DB back running and do a dump of
all the tables once the machine has been moved back to the data center
(hopefully shortly). At the moment it's sitting in an office and has
limited outbound bandwidth.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 3/15/21 6:32 PM, Chris Cason wrote:
> On 16/03/2021 04:04, Ash Holsenback wrote:
>> On 3/15/21 11:11 AM, Chris Cason wrote:
>> last time i touched wikidocgen i was running php7 on my machine so i
>> have /some/ confidence, however i've not kept up with mediawiki
>> changes so i don't know what's in store for that... i'm most fearful
>> of table name changes. didn't that bite us in the ass last time we
>> upgraded?
>
> Your memory is likely better than mine, so perhaps there were. I hope
> there'd be some sort of upgrade script if so.
>
>> we /do/ have a most recent sql dump correct?
>
> We have a backup of the DB (not a dump specifically, just the physical
> DB directory). While I have yet to bring up mysql I don't anticipate
> problems.
>
>> on my machine in a while. do you think there's some value in seeing if
>> i can get that running to see if we can even get it to import?
>
> Yes, that would be great. I'll get the DB back running and do a dump of
> all the tables once the machine has been moved back to the data center
> (hopefully shortly). At the moment it's sitting in an office and has
> limited outbound bandwidth.
>
> -- Chris
ok i did some poking around... first off i'm 2 minor rev's behind on my
opsys and i need to keep it there for the time being, so i think
mediawiki v1.33 is the best i can do (v1.35 is the current supported)...
mainly because i'm at php7.2.5
https://en.wikipedia.org/wiki/MediaWiki_version_history
worth continuing?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 3/15/21 6:32 PM, Chris Cason wrote:
> On 16/03/2021 04:04, Ash Holsenback wrote:
>> On 3/15/21 11:11 AM, Chris Cason wrote:
>> last time i touched wikidocgen i was running php7 on my machine so i
>> have /some/ confidence, however i've not kept up with mediawiki
>> changes so i don't know what's in store for that... i'm most fearful
>> of table name changes. didn't that bite us in the ass last time we
>> upgraded?
>
> Your memory is likely better than mine, so perhaps there were. I hope
> there'd be some sort of upgrade script if so.
>
>> we /do/ have a most recent sql dump correct?
>
> We have a backup of the DB (not a dump specifically, just the physical
> DB directory). While I have yet to bring up mysql I don't anticipate
> problems.
>
>> on my machine in a while. do you think there's some value in seeing if
>> i can get that running to see if we can even get it to import?
>
> Yes, that would be great. I'll get the DB back running and do a dump of
> all the tables once the machine has been moved back to the data center
> (hopefully shortly). At the moment it's sitting in an office and has
> limited outbound bandwidth.
>
> -- Chris
forged ahead... i have v1.33.4 wiki testbed running
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 18/03/2021 04:42, Ash Holsenback wrote:
> forged ahead... i have v1.33.4 wiki testbed running
thanks ... As the wiki ran in a jail (kind of like a lite vm with its
own ip adress, daemons and login accounts), it and other related sites
like the texlib etc are last on the list of things I have to recover.
[This is primarily because the jailed processed get a clone of pretty
much the entire server environment and there's no point in cloning it
until I've finished setting the server up.]
If you need data from the server pre-crash I have the wiki db recovered
already and dumped to .sql files (10mb compressed), a tarball of the
http directory (117mb compressed), and a tarball of your home directory
(1.2gb compressed). Just LMK what you need and I'll email you a link.
[If you need the latter it may need to wait until the machine has been
moved back to the DC as the outbound bandwidth at the office is a bit
more limited than the DC.]
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Current status: The main database (user registrations, front-page news
items, links, redirects, and a bunch of other stuff) has been recovered
and upgraded to mysql 5.7. I'm in the process of converting all the PHP
code that talks to it to use mysqli as PHP 7 dropped the old mysql
driver. The parts of it that I've done so far seem to work OK.
The news.povray.org forums database has also been dumped and recovered
in 5.7 and seems OK but I have yet to start on the code conversion.
The povray.org and irtc.org FTP servers are now running again.
The mail server is now accepting mail from outside.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 3/17/21 9:57 PM, Chris Cason wrote:
> On 18/03/2021 04:42, Ash Holsenback wrote:
>> forged ahead... i have v1.33.4 wiki testbed running
>
> thanks ... As the wiki ran in a jail (kind of like a lite vm with its
> own ip adress, daemons and login accounts), it and other related sites
> like the texlib etc are last on the list of things I have to recover.
>
> [This is primarily because the jailed processed get a clone of pretty
> much the entire server environment and there's no point in cloning it
> until I've finished setting the server up.]
>
> If you need data from the server pre-crash I have the wiki db recovered
> already and dumped to .sql files (10mb compressed), a tarball of the
> http directory (117mb compressed), and a tarball of your home directory
> (1.2gb compressed). Just LMK what you need and I'll email you a link.
>
> [If you need the latter it may need to wait until the machine has been
> moved back to the DC as the outbound bandwidth at the office is a bit
> more limited than the DC.]
>
> -- Chris
email me a link when you get a moment... all i need for now is wiki db
and my home directory. i'm also playing with skins for the wiki...
figured i'd update the /look/ as well
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 3/18/21 6:59 AM, Ash Holsenback wrote:
> email me a link when you get a moment... all i need for now is wiki db
> and my home directory. i'm also playing with skins for the wiki...
> figured i'd update the /look/ as well
btw: take yer time... i've had enough for a day or two
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2021-03-14 10:10 PM (-4), Chris Cason wrote:
> Folks,
>
> The povray.org server had a catastrophic hardware failure on March 9 and
> it was decided that the best course was to replace it completely.
Thank you, thank you, thank you, thank you, thank you!
> Finally, I'd like at this point to give a MASSIVE shout-out to Andrew at
> Netplex Internet in CT, who not only provided us with the replacement
> server (a HP DL360 G5 that they were no longer using) but also stayed up
> until 5am on Saturday getting it set up and configured to the point
> where I could remotely log in and start the setup.
And thank them, too!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 3/17/21 10:14 PM, Chris Cason wrote:
> Current status: The main database (user registrations, front-page news
> items, links, redirects, and a bunch of other stuff) has been recovered
> and upgraded to mysql 5.7. I'm in the process of converting all the PHP
> code that talks to it to use mysqli as PHP 7 dropped the old mysql
> driver. The parts of it that I've done so far seem to work OK.
>
> The news.povray.org forums database has also been dumped and recovered
> in 5.7 and seems OK but I have yet to start on the code conversion.
>
> The povray.org and irtc.org FTP servers are now running again.
>
> The mail server is now accepting mail from outside.
>
> -- Chris
>
>
is see an issue on this page: http://www.povray.org/documentation/
v3.7 seems ok but selecting v3.6 then try to drill down... sends you
back to choice page
also on http://www.povray.org/download/ ... hover around a bit and
notice some of text gets under-lined red. style sheet?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
