Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: Sock Error?  (Read 4285 times)

0 Members and 1 Guest are viewing this topic.

Will Estes

  • Anope User
  • Offline Offline
  • Posts: 3
Sock Error?
« on: December 13, 2012, 12:59:50 AM »

Setting up services currently with UnrealIRCd. I got everything configured and I get this error flooding the log file. My harddrive space was slowly disappearing. Heres what the log spewed:

Code: [Select]
$ head -20 services.log.20121213
[Dec 13 00:57:47 2012] SERVER: services.*************.com (Services for IRC) uplinked to no uplink connected to the network
[Dec 13 00:57:47 2012] Anope 1.9.8-may-cause-insanity starting up
[Dec 13 00:57:47 2012] Loading modules...
[Dec 13 00:57:49 2012] Using IRCd protocol unreal
[Dec 13 00:57:49 2012] Loading databases...
[Dec 13 00:57:49 2012] Databases loaded
[Dec 13 00:57:49 2012] Attempting to connect to uplink #1 127.0.0.1 (127.0.0.1), port 8001
[Dec 13 00:57:49 2012] Successfully connected to uplink #1 127.0.0.1:8001
[Dec 13 00:57:49 2012] SockEngine::Process(): error: Bad file descriptor
[Dec 13 00:57:49 2012] SockEngine::Process(): error: Bad file descriptor
[Dec 13 00:57:49 2012] SockEngine::Process(): error: Bad file descriptor
[Dec 13 00:57:49 2012] SockEngine::Process(): error: Bad file descriptor
[Dec 13 00:57:49 2012] SockEngine::Process(): error: Bad file descriptor
[Dec 13 00:57:49 2012] SockEngine::Process(): error: Bad file descriptor
[Dec 13 00:57:49 2012] SockEngine::Process(): error: Bad file descriptor
[Dec 13 00:57:49 2012] SockEngine::Process(): error: Bad file descriptor
[Dec 13 00:57:49 2012] SockEngine::Process(): error: Bad file descriptor
[Dec 13 00:57:49 2012] SockEngine::Process(): error: Bad file descriptor
[Dec 13 00:57:49 2012] SockEngine::Process(): error: Bad file descriptor
[Dec 13 00:57:49 2012] SockEngine::Process(): error: Bad file descriptor

Any help is much appreciated.
Logged

katsklaw

  • Supporter
  • Anope User
  • Offline Offline
  • Posts: 537
Re: Sock Error?
« Reply #1 on: December 13, 2012, 01:39:21 AM »

There are a few things that can cause this error. You said your HD space was disappearing, lets start there and see how much space you have left.

If you are root on the machine or know for a fact you don't have a quota: df -h

If you have a shell and have a quota, contact your provider about how to check your free space.

The reason this is important is that *nix systems see everything as files. Sockets, file descriptors, everything and if you are at your quota then you can't create new sockets(files).

It's also a good idea to insure Anope isn't already running.
« Last Edit: December 13, 2012, 01:44:27 AM by katsklaw »
Logged

Will Estes

  • Anope User
  • Offline Offline
  • Posts: 3
Re: Sock Error?
« Reply #2 on: December 13, 2012, 01:58:37 AM »

I meant I was running out of space because of the log spam.

And I made sure it was the only instance running.
Logged

katsklaw

  • Supporter
  • Anope User
  • Offline Offline
  • Posts: 537
Re: Sock Error?
« Reply #3 on: December 13, 2012, 02:16:06 AM »

The next thing I'd suggest is running fsdk in single user mode after insuring nothing else is on that IP and port. Perhaps netstat -lnptu
Logged

Will Estes

  • Anope User
  • Offline Offline
  • Posts: 3
Re: Sock Error?
« Reply #4 on: December 13, 2012, 02:20:41 AM »

Unreal responds on port 8001. Just confirmed with netcat.
Logged
Pages: [1]   Go Up