Ladies and gentlemen, the server is up again.
yea, sorry about the delay on getting the server back up and running,
it seems that after a cPanel and/OR CentOS update, every shell user was set down to a 512mb memory limit, but minecraft server needs at least 1gb of ram.
Code:
[11:53:38] <LoganA> Cue: how big is your quota?
[11:53:50] <Cue> LoganA: Unlimited
[11:54:02] <Cue> And we don't have RAM quotas
[11:54:07] <Alam_Squeeze> ulimit -m -v
[11:54:17] <Alam_Squeeze> max memory size (kbytes, -m) 524288
[11:54:17] <Alam_Squeeze> virtual memory (kbytes, -v) 524288
[11:54:26] <Cue> Okay so one of you lowered it then?
[11:54:43] <LoganA> yea, there are ram qoutas
[11:54:59] <Cue> When did this happen? D:
[11:55:08] <ZarroTsu> inb4 alam
[11:55:10] <LoganA> cpanel update?
[11:55:15] <Alam_Squeeze> CentOS update?
[11:55:39] -*- Cue CentOS rages
[11:55:39] <LoganA> hmmm, on my user, it is unlimited
[11:56:01] <Alam_Squeeze> LoganA: on the server?
[11:56:09] <LoganA> yes
[11:56:52] <Alam_Squeeze> really? Ubuntu and Debian have it set to unlimited but alam@srb2.org set to 512MB
[11:57:16] <LoganA> logan@logan.srb2.org [~]# ulimit -m -v
[11:57:16] <LoganA> max memory size (kbytes, -m) unlimited
[11:57:16] <LoganA> virtual memory (kbytes, -v) unlimited
[11:57:31] <LoganA> also, it's a screen session
[11:58:19] <LoganA> I started a new session, without screen, not it's 512mb limit
[11:58:24] <LoganA> *now it's
[11:58:44] <Alam_Squeeze> heh, so PAM's /etc/security/limits.conf changed
[12:00:04] <Cue> because an update that adds in memory limits is always a good idea :x
[12:00:19] <Alam_Squeeze> no, it looks like libpam.so default's limit was changed
[12:00:25] <Cue> O.o
[12:00:54] <ZarroTsu> I would think it IS a good idea to force a limit on something upon an update or elsewise, due to the fact that accidental instability would be very very bad
[12:01:13] <Cue> ZarroTsu: Without letting you configure it, it's not
[12:01:28] <Alam_Squeeze> well, I can overwrite the limits
[12:01:30] <ZarroTsu> developers don't care; they assume everyone is stupider then they are :V
[12:01:38] <Cue> "Oh hey, they didn't cap users, let's do it anyways!"
[12:01:44] <Cue> I don't like CentOS but Ubuntu has no cPanel D:
[12:01:53] <Cue> (Debian's repos are old as fuck ;_;)
[12:02:23] <LoganA> give only cue upped memory limits
[12:02:50] <Alam_Squeeze> well, wait, I am being lazy again
[12:03:52] <ZarroTsu> THAT'S OUR ALAM! *laughter* *applause* WE-HE'LL BE RIGHT BACK, AFTER THESE MESSAGES. *fade-out*
[12:05:20] <Alam_Squeeze> yea, I modifing my Mono's limit.conf to move's logan and @pulse-rt to it's own files
[12:05:55] <LoganA> ZarroTsu: lazy means, "hold on, let me find out how to do this shit"
[12:06:16] <ZarroTsu> in the most open terminology available
[12:06:36] <Alam_Squeeze> heh, this way, when Debian updated my limit.conf file, it does not lose it settings
[12:08:39] <LoganA> let me ask, ZarroTsu, do you know how to setup pam limits?
[12:09:06] <ZarroTsu> nope
[12:09:12] <ZarroTsu> I've no reason to look into it
[12:09:19] <ZarroTsu> excluding "the future"
[12:09:49] <ZarroTsu> I'm still looking for a job that accepts me for basic B-plus level college graduate network skills
[12:10:01] <ZarroTsu> until THAT happens, I'm no insightive to learn anything
[12:14:47] <Alam_Squeeze> LoganA: login into Cue account again, and see if the ulimit changed
[12:15:03] <Cue> still the same
[12:16:00] <Alam_Squeeze> again!
[12:17:09] <Cue> nope
[12:18:15] <Alam_Squeeze> again! maybe I need to restart the OpenSSH daemon for the PAM setting to take effect
[12:18:21] <LoganA> http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/sag-pam_limits.html ?
[12:18:23] <Cue> nope
[12:19:08] <Alam_Squeeze> or it may help if the sshd pam config had pam_limits.so!
[12:19:11] <Alam_Squeeze> grrr....
[12:20:18] <Alam_Squeeze> no, it include system-auth, which have pam_limits.so
[12:25:50] -*- Cue sits here with a watch -n 1 on ulimit -m -v
[12:26:20] <Alam_Squeeze> you need to logout and login to take effect
[12:26:41] <Cue> Still the same
[12:26:42] <Alam_Squeeze> you had been login and out of sshd to check on ulimit, right?
[12:26:52] <Cue> yeah
[12:27:21] <Alam_Squeeze> Logan, you did restart sshd on each limits.conf change, right?
[12:31:50] <Alam_Squeeze> ulimit -a -S; ulimit -a -H
[12:32:57] <Alam_Squeeze> only the core size and stack size can be modified
[12:35:34] <Alam_Squeeze> heh
[12:49:19] <Scizor300> Yeah, locking you two out would not be good ;-;
[12:49:39] <Scizor300> The JVM wouldn't be fixed
[12:52:24] <Alam_Squeeze> heh, updating my CentOS VM to 5.6
[14:02:31] <Alam_Squeeze> Cue: try now
[14:04:35] <Cue> nope :<
[14:04:39] <Cue> cue@server:~/minecraft_new$ ulimit -v -m
[14:04:39] <Cue> virtual memory (kbytes, -v) 524288
[14:04:39] <Cue> max memory size (kbytes, -m) unlimited
[14:05:43] <Alam_Squeeze> what? you need unlimited virtual memory?
[14:06:58] <Alam_Squeeze> Cue: now
[14:07:32] <Cue> Vrrruuuuup
[14:08:24] <Cue> And we're live
[14:08:26] <Cue> Cheers Alam