[Indimail-support] unable to open supervise/ok: file does not exist
Mohan L
I trying to install indimail on RHEL 6 using rpm. It is not showing
any error while installaing the indimail. It shows "unable to open
supervise/ok: file does not exist" for all the service while checking
service stats using svstat.
Machine Hardware Architecture :
$ uname -m
x86_64
Linux Distribution:
$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.0 (Santiago)
MySQL Version :
$ mysql_config --version
5.1.47
RPM Download Path :
$ wget -c http://download.opensuse.org/repositories/home:/indimail/RedHat_RHEL-6/x86_64/indimail-1.8.3-1.2.x86_64.rpm
Here is the steps and output :
Step : I
$ sudo rpm -ivh indimail-1.8.3-1.2.x86_64.rpm
warning: indimail-1.8.3-1.2.x86_64.rpm: Header V3 DSA/SHA1 Signature,
key ID daba51f0: NOKEY
Preparing...
########################################### [100%]
Checking for mandatory user/group mysql..
Adding IndiMail users/groups
1:indimail
########################################### [100%]
Creating /var/log/indimail
Creating Database/Service for MySQL
Creating /var/indimail/etc/indimail.cnf
Creating MySQL database in /var/indimail/mysqldb/data
Installing MySQL system tables...
OK
Filling help tables...
OK
To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system
PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/bin/mysqladmin -u root password 'new-password'
/usr/bin/mysqladmin -u root -h TCL password 'new-password'
Alternatively you can run:
/usr/bin/mysql_secure_installation
which will also give you the option of removing the test
databases and anonymous user created by default. This is
strongly recommended for production servers.
See the manual for more instructions.
You can start the MySQL daemon with:
cd /usr ; /usr/bin/mysqld_safe &
You can test the MySQL daemon with mysql-test-run.pl
cd /usr/mysql-test ; perl mysql-test-run.pl
Please report any problems with the /usr/scripts/mysqlbug script!
Creating MySQL Database in /var/indimail/mysqldb/data with defaults
file /var/indimail/etc/indimail.cnf
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
111129 22:30:37 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
111129 22:30:37 InnoDB: Log file ./ib_logfile0 did not exist: new to
be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
111129 22:30:37 InnoDB: Log file ./ib_logfile1 did not exist: new to
be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
111129 22:30:37 InnoDB: Started; log sequence number 0 0
111129 22:30:37 InnoDB: Starting shutdown...
111129 22:30:42 InnoDB: Shutdown completed; log sequence number 0
44233
Creating MySQL Service Port 3306, Service /service, conf file /var/
indimail/etc/indimail.cnf
indimail._domainkey IN TXT "k=rsa;
p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCaXANq8h9tAmXRaHB9Iy8fFQcMFdrKo
+tQb3aTS0aLnfNJKfMlAkZFSZklLJP9ec26fu3YyUlI0vzwad190u3kiI
+8hjOFtDv3dAaOU3zLr8ms9VQP0APIyVeASgaM0fEGb9/8P0FbLBHJ9qJOUlNDfhFC/
Zqa9549SMXqHVj0GQIDAQAB"
Creating SMTP Listener Port 465, Service /service, Queue Base /var/
indimail/queue, Queue Count 5, Queue Start 1
Creating 5 queues
Creating Queue /var/indimail/queue/nqueue
Creating Queue /var/indimail/queue/queue1
Creating Queue /var/indimail/queue/queue2
Creating Queue /var/indimail/queue/queue3
Creating Queue /var/indimail/queue/queue4
Creating Queue /var/indimail/queue/queue5
Creating SMTP Listener Port 25, Service /service, Queue Base /var/
indimail/queue, Queue Count 5, Queue Start 1
Creating SMTP Listener Port 587, Service /service, Queue Base /var/
indimail/queue, Queue Count 5, Queue Start 1
Creating queue envdir defaultqueue
Creating SMTP Listener Port 366, Service /service
Creating QMTP Listener Port 209, Service /service, Queue Base /var/
indimail/queue, Queue Count 5, Queue Start 1
Creating QMQP Listener Port 628, Service /service, Queue Base /var/
indimail/queue, Queue Count 5, Queue Start 1
Creating FetchMail Daemon Service /service, Queue Base /var/indimail/
queue, Queue Count 5, Qstart 1
Creating IMAP4 Listener Port 143, Service /service
Creating IMAP4 Listener Port 993, Service /service
Creating POP3 Listener Port 110, Service /service
Creating POP3 Listener Port 995, Service /service
Creating IMAP4 Listener Port 4143, Service /service
Creating IMAP4 Listener Port 9143, Service /service
Creating POP3 Listener Port 4110, Service /service
Creating POP3 Listener Port 9110, Service /service
Creating IndiMail Admin Service Port 4000, Service /service, Base
Path /home/mail
Creating InLookup Daemon on Fifo infifo, Service /service, Threads 5
Creating pwdLookup Daemon on socket /tmp/nssd.sock, Service /service,
Threads 5
Creating /var/indimail/etc/nssd.conf
Creating poppass Listener Port 106, Service /service use_ssl=1
Creating /var/indimail/etc/clamd.conf
Creating /var/indimail/etc/freshclam.conf
Creating Virus Scanner Service ClamdPrefix /var/indimail, Service /
service
Creating /var/indimail/etc/bogofilter.cf
Creating Default Control Files
me
defaultdomain
plusdomain
locals
rcpthosts
Your fully qualified host name is TCL.
Putting TCL into /var/indimail/control/me...
Putting TCL into control/defaultdomain...
Putting TCL into /var/indimail/control/plusdomain...
grep: /var/indimail/control/virtualdomains: No such file or directory
Putting TCL into /var/indimail/control/locals...
Putting TCL into /var/indimail/control/rcpthosts...
Now qmail will refuse to accept SMTP messages except to TCL.
Make sure to change rcpthosts if you add hosts to locals or
virtualdomains!
Setting Following Files to Reasonable Defaults
defaultdelivery
defaulthost
envnoathost
nodnscheck
localiphost
hostip
smtpgreeting
databytes
timeoutsmtpd
timeoutremote
chkrcptdomains
greylist.white
assign
dnsbllist
tcp.smtp
tcp.qmtp
tcp.qmqp
tcp.imap
tcp.pop3
tcp.poppass
procmailrc
host.mysql
Creating catch-all alias (/var/indimail/alias/Maildir) for all system
users
Creating CDB /var/indimail/etc/tcp.smtp.cdb
Creating CDB /var/indimail/etc/tcp.qmtp.cdb
Creating CDB /var/indimail/etc/tcp.qmqp.cdb
Creating CDB /var/indimail/etc/tcp.imap.cdb
Creating CDB /var/indimail/etc/tcp.pop3.cdb
Creating CDB /var/indimail/etc/tcp.poppass.cdb
Creating svscan log Service Service /service
adding indimail startup
Installing upstart service
svscan stop/waiting
1. Issue /sbin/initctl emit qmailstart to start services
2. Change your default domain in /var/indimail/control/defaultdomain
3. You can optionally run the following command to verify installation
sudo rpm -V indimail
4. You also need to create CERTS for IMAP/POP3. run the following
command to create cert
/var/indimail/sbin/svctool --postmaster=postm...@indimail.org --
config=cert
Step : II
$ sudo /etc/init.d/mysqld stop
Stopping mysqld: [ OK ]
$ sudo chkconfig mysqld off
$ sudo rm -f /service/mysql.3306/down
Step : III
$ sudo /var/indimail/bin/svstat /service/*
/service/clamd: unable to open supervise/ok: file does not exist
/service/fetchmail: unable to open supervise/ok: file does not exist
/service/freshclam: unable to open supervise/ok: file does not exist
/service/greylist.1999: unable to open supervise/ok: file does not
exist
/service/indisrvr.4000: unable to open supervise/ok: file does not
exist
/service/inlookup.infifo: unable to open supervise/ok: file does not
exist
/service/mysql.3306: unable to open supervise/ok: file does not exist
/service/proxy-imapd.4143: unable to open supervise/ok: file does not
exist
/service/proxy-imapd-ssl.9143: unable to open supervise/ok: file does
not exist
/service/proxy-pop3d.4110: unable to open supervise/ok: file does not
exist
/service/proxy-pop3d-ssl.9110: unable to open supervise/ok: file does
not exist
/service/pwdlookup: unable to open supervise/ok: file does not exist
/service/qmail-imapd.143: unable to open supervise/ok: file does not
exist
/service/qmail-imapd-ssl.993: unable to open supervise/ok: file does
not exist
/service/qmail-pop3d.110: unable to open supervise/ok: file does not
exist
/service/qmail-pop3d-ssl.995: unable to open supervise/ok: file does
not exist
/service/qmail-poppass.106: unable to open supervise/ok: file does not
exist
/service/qmail-qmqpd.628: unable to open supervise/ok: file does not
exist
/service/qmail-qmtpd.209: unable to open supervise/ok: file does not
exist
/service/qmail-send.25: unable to open supervise/ok: file does not
exist
/service/qmail-smtpd.25: unable to open supervise/ok: file does not
exist
/service/qmail-smtpd.366: unable to open supervise/ok: file does not
exist
/service/qmail-smtpd.465: unable to open supervise/ok: file does not
exist
/service/qmail-smtpd.587: unable to open supervise/ok: file does not
exist
/service/qmail-spamlog: unable to open supervise/ok: file does not
exist
/service/qscanq: unable to open supervise/ok: file does not exist
I am not able to figure out what I am doing wrong. I guess some
synbolic link to the shared library is broken in my system. See the
bellow output : Even I am getting the bellow after installing indimail-
devel :
$rpm -V indimail
instcheck: warning: /var/indimail/man/man3 does not exist
instcheck: warning: unable to stat .../libcdb.so: file does not exist
instcheck: warning: unable to stat .../libeps.so: file does not exist
instcheck: warning: unable to stat .../libflash.so: file does not
exist
instcheck: warning: unable to stat .../libindimail.so: file does not
exist
instcheck: warning: unable to stat .../libnss_nssd.so.2.0.0: file does
not exist
create_table: Failed to open local db
failed to create table indimail
mysql_real_connect: localhost: Can't connect to local MySQL server
through socket '/tmp/mysql.sock' (2)
install_tables returned non-zero exit status. Check Installation
! Potential problems were found with your IndiMail installation in /
var/indimail
instcheck: warning: /var/indimail/man/man3 does not exist
instcheck: warning: unable to stat .../libcdb.so: file does not exist
instcheck: warning: unable to stat .../libeps.so: file does not exist
instcheck: warning: unable to stat .../libflash.so: file does not
exist
instcheck: warning: unable to stat .../libindimail.so: file does not
exist
instcheck: warning: unable to stat .../libnss_nssd.so.2.0.0: file does
not exist
create_table: Failed to open local db
failed to create table indimail
mysql_real_connect: localhost: Can't connect to local MySQL server
through socket '/tmp/mysql.sock' (2)
install_tables returned non-zero exit status. Check Installation
! Potential problems were found with your IndiMail installation in /
var/indimail
Even I am getting the above after installing indimail-devel .
Thanks & Rg
Mohan L
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Indimail-support mailing list
Indimail...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/indimail-support
Manvendra Bhangui
> Hi Manny,
>
> I trying to install indimail on RHEL 6 using rpm. It is not showing
> any error while installaing the indimail. It shows "unable to open
> supervise/ok: file does not exist" for all the service while checking
> service stats using svstat.
>
>
svscan. If svscan is not running, it means that you have not started
indimail
> Installing upstart service
> svscan stop/waiting
> 1. Issue /sbin/initctl emit qmailstart to start services
You have forgotten the above step to start indimail. Start indimail by doing
initctl emit qmailstart
or
service indimail start
or
/etc/init.d/indimail start
or
/var/indimail/sbin/initsvc -on
Mohan L
>OK. This error means supervise is not running. supervise is started by
svscan. If svscan is not running, it means that you have not started
indimail
You have forgotten the above step to start indimail. Start indimail by doing
> Installing upstart service
> svscan stop/waiting
> 1. Issue /sbin/initctl emit qmailstart to start services
initctl emit qmailstart
or
service indimail start
or
/etc/init.d/indimail start
or
/var/indimail/sbin/initsvc -on
$ sudo /var/indimail/sbin/initsvc -status
svscan start/running, process 2052
Now I have restarted it but still I am getting "unable to open supervise/ok" .
$ sudo /var/indimail/sbin/initsvc -off
svscan stop/waiting
$ sudo /var/indimail/sbin/initsvc -on
svscan start/running, process 16349
$ sudo /var/indimail/bin/svstat /service/*
/service/clamd: unable to open supervise/ok: file does not exist
/service/fetchmail: unable to open supervise/ok: file does not exist
/service/freshclam: unable to open supervise/ok: file does not exist
/service/greylist.1999: unable to open supervise/ok: file does not exist
etc......
Manvendra Bhangui
This means that supervise is not running. what is the output of
ps axww |grep svscan
Mohan L
$ ps axww |grep svscan
17918 pts/0 S+ 0:00 grep svscan
- Mohan L
Manvendra Bhangui
So that means that svscan is not running. This looks like an issue
with initctl or the job control file that indimail has for svscan.
Also this is RHEL6. Do a man page of initctl and see if the indimail
job control file (i think /etc/event.d/svscan) has the right grammar.
# initctl status svscan
Manvendra Bhangui
> On Wed, Nov 30, 2011 at 7:55 AM, Mohan L <l.moh...@gmail.com> wrote:
>>> This means that supervise is not running. what is the output of
>>> ps axww |grep svscan
>>
>>
>> $ ps axww |grep svscan
>> 17918 pts/0 S+ 0:00 grep svscan
>>
>
> So that means that svscan is not running. This looks like an issue
> with initctl or the job control file that indimail has for svscan.
> Also this is RHEL6. Do a man page of initctl and see if the indimail
> job control file (i think /etc/event.d/svscan) has the right grammar.
>
> # initctl status svscan
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Technical_Notes/deployment.html
As per the above documents, the job control files should be in
/etc/init. Check if the file /etc/init/svscan has any problem.
--
Regards Manvendra - http://www.indimail.org