Like Ra's Naughty Forum
Site performance, Server errors, outages and tunings - Printable Version

+- Like Ra's Naughty Forum (https://www.likera.com/forum/mybb)
+-- Forum: Technical section (https://www.likera.com/forum/mybb/Forum-Technical-section)
+--- Forum: Site (https://www.likera.com/forum/mybb/Forum-Site)
+--- Thread: Site performance, Server errors, outages and tunings (/Thread-Site-performance-Server-errors-outages-and-tunings)



RE: Site performance, Server errors, outages and tunings - Like Ra - 14 Nov 2011

The VPS was down for 1 hour again. But now I think I understand what's going on.

At 12:01 all VPS'es (except mine) begin to process 24-hour logs thus overloading the disk.

A ticket has been logged. Waiting for a response.


RE: Site performance, Server errors, outages and tunings - Like Ra - 14 Nov 2011

BTW, they replaced a disk on Saturday.


RE: Site performance, Server errors, outages and tunings - Like Ra - 15 Nov 2011

(13 Nov 2011, 16:12 )krinlyc Wrote: nice

Yep, love it. I have several rules for simultaneous connections per IP, per site directory and total requests per IP within 10min. All rules work - seen in the logs.

I'm beginning to get more fun from tweaking, than from the actual content 😁


RE: Site performance, Server errors, outages and tunings - madjack - 16 Nov 2011

Have you switched of the code 'validation' for comments against your Blog?

....or is this another feature designed to challange your mighty bug fixing talent?

😁

MJ


RE: Site performance, Server errors, outages and tunings - Like Ra - 16 Nov 2011

(16 Nov 2011, 14:41 )madjack Wrote: Have you switched of the code 'validation'

Yeah, removed the captcha for several reasons.

o- if you enter a wrong code, you will lose you comment and have to type from scratch, what is very frustrating
o- additional code to load
o- it creates a session file with a code on disk and I would like to reduce disk operations as much as possible
o- Internet community finds captchas annoying, many people simply refuse to leave comments
o- captcha does not prevent SPAM completely. I was getting ~10-15 SPAM a day with captcha (~50-70 without)


RE: Site performance, Server errors, outages and tunings - Like Ra - 17 Nov 2011

Finally I've got some attention from the provider! They are going to change the other VPSes' crontabs to distribute the load. Yeeeehhaaaa!!!! Took me 8 months to convince them.


RE: Site performance, Server errors, outages and tunings - krinlyc - 17 Nov 2011

(17 Nov 2011, 16:53 )Like Ra Wrote: Finally I've got some attention from the provider! They are going to change the other VPSes' crontabs to distribute the load. Yeeeehhaaaa!!!! Took me 8 months to convince them.

Cool - very good - well done
krinlyc


RE: Site performance, Server errors, outages and tunings - Like Ra - 18 Nov 2011

Something happened with DNS today. The likera.com was not resolvable. Had to restart named several times.


RE: Site performance, Server errors, outages and tunings - Like Ra - 18 Nov 2011

Don't get it:

Nov 18 04:09:38 likera named[18781]: listening on IPv4 interface lo, 127.0.0.1#53
Nov 18 04:09:38 likera named[18781]: could not listen on UDP socket: address family not supported
Nov 18 04:09:38 likera named[18781]: creating IPv4 interface lo failed; interface ignored
Nov 18 04:09:38 likera named[18781]: listening on IPv4 interface seth0, x.x.x.x#53
Nov 18 04:09:38 likera named[18781]: could not listen on UDP socket: address family not supported
Nov 18 04:09:38 likera named[18781]: creating IPv4 interface seth0 failed; interface ignored
Nov 18 04:09:38 likera named[18781]: listening on IPv4 interface seth0:cp1, y.y.y.y#53
Nov 18 04:09:38 likera named[18781]: could not listen on UDP socket: address family not supported
Nov 18 04:09:38 likera named[18781]: creating IPv4 interface seth0:cp1 failed; interface ignored
Nov 18 04:09:38 likera named[18781]: not listening on any interfaces

Never seen that before. It was not working since 5 hours ago. Nice ...


RE: Site performance, Server errors, outages and tunings - Like Ra - 18 Nov 2011

Looks like another bug in either kernel or named. Had to explicitly set the maximum open files limit. Weird ...