Your message dated Thu, 05 Jun 2014 00:44:45 +0200
with message-id <[email protected]>
and subject line Re: Bug#710283: inspircd: Starting Inspircd fails on writing 
to PID file
has caused the Debian Bug report #710283,
regarding inspircd: Starting Inspircd fails on writing to PID file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
710283: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710283
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: inspircd
Version: 2.0.5-1+b1
Severity: grave
Tags: upstream
Justification: renders package unusable

After configuration Inspircd always fails to start with the following error in 
/var/log/inspircd.log
"Wed May 29 16:33:24 2013: Failed to write PID-file 'data/inspircd.pid', 
exiting." But in the config file the pid file location is configured as 
/var/run/inspircd.pid

-- System Information:
Debian Release: 7.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages inspircd depends on:
ii  libc6             2.13-38
ii  libgcc1           1:4.7.2-5
ii  libgeoip1         1.4.8+dfsg-3
ii  libgnutls26       2.12.20-6
ii  libldap-2.4-2     2.4.31-1+nmu2
ii  libmysqlclient18  5.5.31+dfsg-0+wheezy1
ii  libpcre3          1:8.30-5
ii  libpq5            9.2.4-1.pgdg70+1
ii  libsqlite3-0      3.7.13-1+deb7u1
ii  libstdc++6        4.7.2-5
ii  libtre5           0.8.0-3
ii  lsb-base          4.1+Debian8
ii  zlib1g            1:1.2.7.dfsg-13

inspircd recommends no packages.

Versions of packages inspircd suggests:
pn  gnutls-bin    <none>
pn  ldap-server   <none>
pn  mysql-server  <none>
pn  postgresql    <none>
pn  sqlite3       <none>

-- Configuration Files:
/etc/default/inspircd changed:
INSPIRCD_ENABLED=1

/etc/inspircd/inspircd.conf changed:
<pid file="/var/run/inspircd.pid" />
----- Cut Irrelevant Parts of Config file -----

-- no debconf information

--- End Message ---
--- Begin Message ---
fixed 710283 2.0.16
thanks

Le vendredi 07 juin 2013 à 09:07 +0200, Tim Gouma a écrit :
> OK,
> 
> You are right, this was wrong and was a result of trying everything I 
> could think off to get it running. But even when fixed this did not 
> solve the problem.
> 
> Because the error message said it couldn't write the PID file, I was 
> searching for problems with writing the PID file. Pretty obvious right?
> 
> Well it seemed to be something completely irrelevant. Because I also had 
> the following line in my config:
> 
> <server name="irc-server" description="IRC Server" network="MyNetwork">
> 
> As you can see NAME is not an valid Domain-Name, which it should be (but 
> didn't know then). And therefore Inspircd throws an error about not 
> being able to write the config file.
> 
> I suggest to change the severity of this bug to low. Because the server 
> starts fine when your config has no problems. But I think it should 
> throw an relevant error if the config do has problems.
> 
> On 02-06-13 22:29, Guillaume Delacour wrote:
> > Problem with "/"                    ^
> >
> > You've edited your configuration and add a slash before ">", this is why
> > inspircd fails to start (reproduced with wheezy chroot). The correct
> > (package default) directive might be :
> >
> >     <pid file="/var/run/inspircd.pid">
> >
> >
> 

I tried to broke the configuration with 2.0.16 as you firstly made and
now have a message that indicate clearly the error:

Thu Jun  5 00:36:17 2014: There were errors in your configuration file:
Thu Jun  5 00:36:17 2014: ANNOUNCEMENT: Invalid character / in key ()
at /etc/inspircd/inspircd.conf:62:34 (inside tag pid at line 62)

So i can close this bug now, feel free to reopen if necessary (as i'll
prepare upload for 2.0.16 soon).

-- 
Guillaume Delacour <[email protected]>

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply via email to