G'Day GN community,
Our tomcat logs were suddenly getting big due to too many open files:
Sep 1, 2012 5:45:25 PM org.apache.tomcat.util.net.JIoEndpoint$Acceptor run SEVERE: Socket accept failed java.net.SocketException: Too many open files
We set the max number larger and restarted tomcat.
max memory size (kbytes, -m) unlimited
open files (-n) 4096
The GN application, which had been functioning normally before restart, came back up. But it renders only a portion of the interface...as if most of the strings were simply not being parsed.
The site still functions (searches run and return results) but the interface itself is stuffed:
http://74.50.62.108:8080/geonetwork/srv/en/main.home
Can anyone suggest where to start looking for the culprit?
I'm not even sure how to engage with the tomcat logfiles: excess of 1Gb for the past 12 hrs and all I've got is a text editor (bleah!)
Many thanks in advance for any pointers...
JB
--
John Brisbin
Managing Director, BoaB interactive Pty Ltd
POB 248, Mount Molloy QLD 4871
M: 0407 471 565 | P: 07 3103 0574
Skype: boabjohn | Twitter: @boabjohn
m'eh! Sorry for the distress call: problem turned out to be a small piece of rogue html markup that got added to strings.xml
Our service is back up and running again on this fine piece of opensource engineering!
Kind regards,
JB
On 4/09/2012 12:13 PM, John Brisbin wrote:
G'Day GN community,
Our tomcat logs were suddenly getting big due to too many open files:
Sep 1, 2012 5:45:25 PM org.apache.tomcat.util.net.JIoEndpoint$Acceptor
run SEVERE: Socket accept failed java.net.SocketException: Too many open
files
We set the max number larger and restarted tomcat.
max memory size (kbytes, -m) unlimited
open files (-n) 4096
The GN application, which had been functioning normally before restart,
came back up. But it renders only a portion of the interface...as if
most of the strings were simply not being parsed.
The site still functions (searches run and return results) but the
interface itself is stuffed:
http://74.50.62.108:8080/geonetwork/srv/en/main.home
Can anyone suggest where to start looking for the culprit?
I'm not even sure how to engage with the tomcat logfiles: excess of 1Gb
for the past 12 hrs and all I've got is a text editor (bleah!)
Many thanks in advance for any pointers...
JB
--
John Brisbin
Managing Director, BoaB interactive Pty Ltd
POB 248, Mount Molloy QLD 4871
M: 0407 471 565 | P: 07 3103 0574
Skype: boabjohn | Twitter: @boabjohn