This is an unexpected issue: uwsgi was not available in EPEL before, so we build our own RPM packages, but someone submitted uwsgi to EPEL with higher priority and incompatible with iRedMail's package, so this issue happened.

It was fixed in the latest development release of iRedMail and will be available in iRedMail-0.9.2 very soon.

Hi annonman, I think my posting is the "workaround" until 0.9.2 is released.
If you follow the steps I described iRedMail works without any issues.

I can confirm this. Although iredapd and fail2ban are set to start automatically they do not. Starting them manually works and there seem to be no errors. However after a reboot (which is not always monitored) the services do not start. I do not know exactly what iredapd does, but fail2ban not starting is definitely a problem.

Big problem indeed ;-)

I have added two lines to /etc/rc.d/rc.local

/etc/rc.d/init.d/iredapd start
/etc/rc.d/init.d/fail2ban start

But that doesn't work. The services still don't start on reboot.

I don't understand what the problem is, since starting the services manually works without any issues.

I have checked the fail2ban and iredapd logs. All logged information is just informational. There are not even warnings (and no errors). The syslog shows no errors or warnings either (/var/log/messages and lastlog).

iRedAPD and Fail2ban is Python application, but they don't use uwsgi at all, 2 separate issues.

If you run 'chkconfig --level 345 iredapd on', iredapd should auto-start after system reboot. No idea why it doesn't work.

I too have this problem after doing an upgrade. iredapd is running fine but uwsgi fails to start even after reboot.

Ohh btw, I tried to add the sym link hack described above and got an error message that the file exists..
My system CentOS 6.6

hmm, ok.. renaming the file and trying to create the sym link still didn't work, so I copied and renamed the iredadmin.ini file to uwsgi.ini in /etc and it works but only when in console. Trying to run as a service still fails.. It least can start it manually when needing to do any admin work.

Thanks for the help..

I think you misunderstood what I was trying to say.. The service does not start after a reboot on my system
root@# service uwsgi status
uwsgi is stopped
root@# service uwsgi start
root@#
root@# service uwsgi status
uwsgi (pid 1748) is running...

I have tried this after multiple reboots.. and yes it should start at reboot ie:
root@# chkconfig --list | grep 3:on
uwsgi              0:off    1:off    2:off    3:on    4:on    5:on    6:off

Sure, here tis..

[uwsgi]
plugins = python
vhost = true
socket = /var/run/uwsgi_iredadmin.socket
pidfile = /var/run/uwsgi_iredadmin.pid
chown-socket = apache:apache
chmod-socket = 660
uid = iredadmin
gid = iredadmin
enable-threads = true

I can confirm on Centos 6.6 uwsgi, fail2ban and iredapd all start successfully after 0.9.2 fixes.

For some reason the package uwsgi-plugin-python was gone, although it was there before. Maybe when trying to fix the errors I have accidently removed it. Everything works fine now with the fixes described in 0.9.1 -> 0.9.2 tutorial.

However I would like to recommend to change the uwsgi.ini file to the following since the daemonize option is not necessary on current CentOS since this is done by the systemctl service already.

[uwsgi]

logto = /var/log/uwsgi.log

# try to autoload appropriate plugin if "unknown" option has been specified
autoload = true

# enable master process manager
master = true

# spawn 2 uWSGI worker processes
workers = 2

# automatically kill workers on master's death
no-orphans = true

# place timestamps into log
log-date = true

# user identifier of uWSGI processes
#uid = uwsgi

# group identifier of uWSGI processes
#gid = uwsgi

# multi-app deployment
emperor = /etc/uwsgi.d
emperor-tyrant = false

I have also removed the socket config from the default uwsgi.ini file, since I have no other sites running that would require it and iRedAdmin has its own uwsgi socket.