Nexus6/Karith Crashing server

[{A}saxon]

Hi. I have not been able to get the maps Nexus6 or Karith to load onto my server.

The maps are where they should be, every thing is as it should be.
server has been fine for ages i even put new copies of the maps in.

If !map nexus6 or !map Karith is done the server crashes, in the server
file console i have a message that says "server is started but not responding
to pings".

The guys i rent the server from rebooted with all new Tremulous files but the two
maps still crash the server.

To say I'm stumped is an understatement. I have had to remove the maps in fear
they get called upon.

Once again all files are in the correct places.
The server is ThewineBar is open.

Any help in resolving this problem is much appreciated.  

[UniqPhoeniX]

What tremded & qvm, do you have mapconfigs/custom layouts for those maps? In server home base folder should be crashlog.txt, what errors do you see in there?

[David]

Both maps are very large.  Is there a memory limit?

[{A}saxon]

There is no limit  on memory,
the tremded is tremulous.x86 (is this the tremded?)
and i have in place p-g QVM 1.6.5 there are no mods on the server.
and there is no crash.log, It's only those two maps, i did for a while
have in place before this problem- Googles QVM which has the !subnetban
command, i understand that it was this command that was crashing my server
when ever i made changes to Admin.dat then did Readconfig. So i went back to
the p-g qvm. Could it be that Googles qvm changed the Autogen in some way.
but why just effect the two maps? Very weird indeed.

anyway thanks for looking.

[kevlarman]

there's no way of telling unless you can provide the crash log (and preferably a stack trace too)

[{A}saxon]

There is no map config file any where.
other server op's tell me they have one.
would this cause the problem?and where can i get one?
trolled the net for a while but with no luck.

[kevlarman]

There is no map config file any where.
other server op's tell me they have one.
would this cause the problem?

no

[{A}saxon]

Just to let you know. It was a Memory allocating problem with the host, All sorted now.
ty anyway.

[KamikOzzy]

We had this problem on AA for a long time. Ended up just needing to increase sv_hunkmegs, in case anyone else has this problem and it isn't the fault of a hosting company's limit.