About 2 months since Lunatics forum became quite unpleasant place for conversations because of random post disappearances at moment of publication.
And now it dies completely with next error message:

8192: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead
File: /home/simon/www.lunatics.at/Sources/Subs.php
Line: 1137

If someone from KWSN group reading this please do smth...

Might it be somehow related to this post?

---

~W

Might it be somehow related to this post?

Definitely it's related cause all troubles started after moving into cloud... but current site's state isn't direct consequence of that transition.

I noticed that yesterday morning.
Also i want to mention that Joe`s computer had no contact for 4 weeks already.
I hope he is O.K.

---

With each crime and every kindness we birth our future.

I noticed that yesterday morning.
Also i want to mention that Joe`s computer had no contact for 4 weeks already.
I hope he is O.K.

Lets hope it's just connectivity issue with his dialup...

good thing i never deleted the latest installer hrhr

---

I came down with a bad case of i don't give a crap

good thing i never deleted the latest installer hrhr

The Installer is also available on my website and on Cruncher`s Anonymous.
See the sticky thread.

---

With each crime and every kindness we birth our future.

We have had backup sites for the installer for the last several versions.

---

I've emailed Toby, maybe he can get it fixed.

Claggy

I've emailed Toby, maybe he can get it fixed.

Claggy

We will probably need to update to at least version 2 of SMF as version 1 is not compatible with the newer versions of MySQL.

---

I've emailed Toby, maybe he can get it fixed.

Claggy

We will probably need to update to at least version 2 of SMF as version 1 is not compatible with the newer versions of MySQL.

I had a reply from Toby:

I wasn't sure if the blank posts were still a problem. I think I sent
someone a private message at seti about that and didn't hear back.

The preg_replace error is odd. It's because the new server has a newer
version of PHP. But I'm not sure why it wasn't a problem from the
beginning. I wonder if the content of some post triggered the code to
follow a different path...

jonnyv and I poked at it a little last night and I think the error did
move to another line but it's still broken as of right now.

I suppose the "correct" solution would be to move to a current version
of the SMF software. jonnyv seems to think there was something custom
about this installation though that may make migrating difficult. But
I can try setting it up in a separate directory for testing and see
what breaks. I'll try to do that tonight.

Toby

Claggy

Thank you Claggy.

---

With each crime and every kindness we birth our future.

Thank you Claggy.

+1

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

I've emailed Toby, maybe he can get it fixed.

Claggy

We will probably need to update to at least version 2 of SMF as version 1 is not compatible with the newer versions of MySQL.

I had a reply from Toby:

I wasn't sure if the blank posts were still a problem. I think I sent
someone a private message at seti about that and didn't hear back.

The preg_replace error is odd. It's because the new server has a newer
version of PHP. But I'm not sure why it wasn't a problem from the
beginning. I wonder if the content of some post triggered the code to
follow a different path...

jonnyv and I poked at it a little last night and I think the error did
move to another line but it's still broken as of right now.

I suppose the "correct" solution would be to move to a current version
of the SMF software. jonnyv seems to think there was something custom
about this installation though that may make migrating difficult. But
I can try setting it up in a separate directory for testing and see
what breaks. I'll try to do that tonight.

Toby

Claggy

The biggest problem would be the portal software as it is not supported by SMF 2.x.

Probably the closest to it would be EZPortal.

---

And it is up.

---

Great.

---

With each crime and every kindness we birth our future.

And it is up.

Had a couple more emails:

Well then.

I was playing around with creating a separate install that I could
test around with in trying to upgrade SMF. But in the middle I ran out
of disk space. I noticed that the log table was several GB in size
because it is logging all these PHP errors to the database. Then mysql
locked up, probably because of the disk filling up. So I killed mysql
and then after restarting it I truncated the log table. Then suddenly
the site came back online.

I have no idea why it came back. But it is back for now! I guess I'll
keep working on attempting an upgrade though. I'm guessing this
version is riddled with all kinds of bugs and security holes... I'm
afraid the upgrade process may wipe out the custom theme and other
things though. Guess we'll see.

Toby

Claggy

ERR_CONNECTION_TIMED_OUT todays morning.
Anyone can access?

About an hour after your post, straight in. Header of newest post in "News":

Message 55389 - Posted: 21 Dec 2015, 8:50:15 UTC - in response to Message 55387.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

About an hour after your post, straight in. Header of newest post in "News":

Message 55389 - Posted: 21 Dec 2015, 8:50:15 UTC - in response to Message 55387.

And I'm still getting ERR_CONNECTION_TIMED_OUT

Looks like routing issue:

Tracing route to lunatics.kwsn.info [64.22.104.43]
over a maximum of 30 hops:
....
19 144 ms 141 ms 140 ms ae4.mpr3.atl6.us.zip.zayo.com [64.125.31.197]
20 145 ms 145 ms 154 ms 128.177.104.134.IPYX-092136-ZYO.zip.zayo.com [128.177.104.134]
21 145 ms 145 ms 145 ms l3-atl-v1-p40.netdepot.com [209.51.149.106]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Any proxy suggestion?