1 Topic by pbf343 (edited by pbf343 2015-07-01 01:35:39)

  • pbf343
  • Member
  • Offline
  • Registered: 2013-05-30
  • Posts: 243

Topic: CentOS 6.x uwsgi post 502 bad gateway daemonize commented out not send

==== Required information ====
- iRedMail version (check /etc/iredmail-release):
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- Related log if you're reporting an issue:
====

CentOS 6.x
iRedMail 0.9.2
iRedAdmin-Pro SQL 2.1.3

Ran iRedMail installer with Nginx and SOGo options enabled along with all others.
Upon completion no iRedAmin open source URL working.

Moved on to iRedPro where unzipped and ran upgrade_install.sh under tools.
Reboot
Get 502 Gateway error like this thread:
http://www.iredmail.org/forum/topic9459 … inpro.html

Remove Daemonize and reboot vs restart to confirm persistence.
Works on display.
Login to both mail and SOGo site and will not send out e-mail with SMTP error.

SMTP Error (451): Failed to add recipient...
....   4.3.5 Server configuration problem


Maillog
Jun 30 09:22:35 mail02 roundcube: <i1ts2or2> SMTP Error: Failed to add recipient 'A_VALID_EMAIL_PRESENT'. 4.3.5 Server configuration problem (Code: 451) in /var/www/roundcubemail-1.1.1/program/lib/Roundcube/rcube.php on line 1714 (POST /mail/?_task=mail&_unlock=loading1435684957813&_lang=en_US&_framed=1?_task=mail&_action=send)

SOGo reports:
Cannot send message: all recipients are invalid.
Maillog
Jun 30 09:28:07 mail02 postfix/smtpd[2152]: connect from DOMAIN.NAME[127.0.0.1]
Jun 30 09:28:07 mail02 postfix/smtpd[2152]: warning: connect to 127.0.0.1:7777: Connection refused
Jun 30 09:28:07 mail02 postfix/smtpd[2152]: warning: problem talking to server 127.0.0.1:7777: Connection refused
Jun 30 09:28:08 mail02 postfix/smtpd[2152]: warning: connect to 127.0.0.1:7777: Connection refused
Jun 30 09:28:08 mail02 postfix/smtpd[2152]: warning: problem talking to server 127.0.0.1:7777: Connection refused
Jun 30 09:28:08 mail02 postfix/smtpd[2152]: NOQUEUE: reject: RCPT from mail02.DOMAIN.NAME[127.0.0.1]: 451 4.3.5 Server configuration problem; from=<postmaster@domain.namel> to=<e-mail@gmail.com> proto=ESMTP helo=<mail02.domain.name>
Jun 30 09:28:08 mail02 postfix/smtpd[2152]: disconnect from mail02.domain.name[127.0.0.1]


Did use a domain name with weird TLD registered a while ago and DNS records are not clean with reverse DNS, etc. 

So, do not think it is a DNS Issue but that could be confusing the matter some or I'm just wrong. 

Thank you.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,770

Re: CentOS 6.x uwsgi post 502 bad gateway daemonize commented out not send

pbf343 wrote:

Jun 30 09:28:07 mail02 postfix/smtpd[2152]: warning: connect to 127.0.0.1:7777: Connection refused

Please restart iredapd service and try again.

3 Reply by pbf343 (edited by pbf343 2015-07-01 04:32:02)

  • pbf343
  • Member
  • Offline
  • Registered: 2013-05-30
  • Posts: 243

Re: CentOS 6.x uwsgi post 502 bad gateway daemonize commented out not send

ZhangHuangbin wrote:
pbf343 wrote:

Jun 30 09:28:07 mail02 postfix/smtpd[2152]: warning: connect to 127.0.0.1:7777: Connection refused

Please restart iredapd service and try again.

Appears the service was not already running as shows stopped...  Mail sent once started.

service iredapd restart
iredapd is already stopped.
Starting iredapd ...

Can you please tell me where is such control configured and why would it would have been off at boot?  Effectively, is that service being dropped with Nginx implementation?

Do these permissions look correct? 
lrwxrwxrwx   1 root    root      18 Jun 30 16:26 iredapd -> /opt/iRedAPD-1.6.0

Are they a security risk given this:
drwx------.  6 iredapd iredapd 4.0K Jun 30 16:19 iRedAPD-1.6.0



Instructions from /opt/iredapd/INSTALL.md   and service does not start with reboot.

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,770

Re: CentOS 6.x uwsgi post 502 bad gateway daemonize commented out not send

iRedAPD should be marked to auto-start after server reboot, you can check this with command:

# chkconfig --list | grep iredapd

Default permission is:

# chown -R iredapd:iredapd /opt/iRedAPD-1.6.0
# chmod -R 0555 /opt/iRedAPD-1.6.0
# chmod 0500 /opt/iRedAPD-1.6.0/settings.py

settings.py contains several SQL/LDAP account credentials, so it cannot be read by others.

5 Reply by pbf343 (edited by pbf343 2015-07-01 19:15:54)

  • pbf343
  • Member
  • Offline
  • Registered: 2013-05-30
  • Posts: 243

Re: CentOS 6.x uwsgi post 502 bad gateway daemonize commented out not send

ZhangHuangbin wrote:

iRedAPD should be marked to auto-start after server reboot, you can check this with command:

# chkconfig --list | grep iredapd

Default permission is:

# chown -R iredapd:iredapd /opt/iRedAPD-1.6.0
# chmod -R 0555 /opt/iRedAPD-1.6.0
# chmod 0500 /opt/iRedAPD-1.6.0/settings.py

settings.py contains several SQL/LDAP account credentials, so it cannot be read by others.


# chkconfig --list | grep iredapd
iredapd            0:off    1:off    2:on    3:on    4:on    5:on    6:off

Modified ownership & permissions to suggested. 
Then confirmed service was off.
Modified /opt/settings.pyc file name to /opt/settings.pyc.ORIG

Listed files
-r-x------  1 iredapd iredapd 2.6K Jun 30 18:17 settings.py
-r-xr-xr-x  1 iredapd iredapd 1.4K Jun 30 18:17 settings.pyc.ORIG
-r-xr-xr-x. 1 iredapd iredapd 2.4K Jun  2 23:32 settings.py.sample

Started iredapd service (/etc/init.d/iredapd start)

Listed files
-r-x------  1 iredapd iredapd 2.6K Jun 30 18:17 settings.py
-r--------  1 root    root    1.4K Jul  1 06:52 settings.pyc
-r-xr-xr-x  1 iredapd iredapd 1.4K Jun 30 18:17 settings.pyc.ORIG
-r-xr-xr-x. 1 iredapd iredapd 2.4K Jun  2 23:32 settings.py.sample


Appears root does take over the ownership, compile and permissions scenario for the executed code (settings.pyc).


REBOOT the CentOS 6.6 machine.
# /etc/init.d/iredapd status
iredapd is stopped.

# chkconfig --list | grep iredapd
iredapd            0:off    1:off    2:on    3:on    4:on    5:on    6:off

# runlevel
N 3


# tail -30 /var/log/iredapd.log
2015-06-30 16:19:24 INFO Starting iRedAPD (version: 1.6.0, backend: mysql), listening on 127.0.0.1:7777.
2015-06-30 16:19:24 INFO Loading plugin: reject_null_sender
2015-06-30 16:19:24 INFO Loading plugin: amavisd_message_size_limit
2015-06-30 16:19:24 INFO Loading plugin: amavisd_wblist
2015-06-30 16:19:24 INFO Loading plugin: sql_alias_access_policy
2015-06-30 18:01:18 INFO Starting iRedAPD (version: 1.6.0, backend: mysql), listening on 127.0.0.1:7777.
2015-06-30 18:01:18 INFO Loading plugin: reject_null_sender
2015-06-30 18:01:18 INFO Loading plugin: amavisd_message_size_limit
2015-06-30 18:01:18 INFO Loading plugin: amavisd_wblist
2015-06-30 18:01:18 INFO Loading plugin: sql_alias_access_policy
2015-06-30 18:01:58 INFO Starting iRedAPD (version: 1.6.0, backend: mysql), listening on 127.0.0.1:7777.
2015-06-30 18:01:58 INFO Loading plugin: reject_null_sender
2015-06-30 18:01:58 INFO Loading plugin: amavisd_message_size_limit
2015-06-30 18:01:58 INFO Loading plugin: amavisd_wblist
2015-06-30 18:01:58 INFO Loading plugin: sql_alias_access_policy
2015-06-30 18:17:41 INFO Starting iRedAPD (version: 1.6.0, backend: mysql), listening on 127.0.0.1:7777.
2015-06-30 18:17:41 INFO Loading plugin: reject_null_sender
2015-06-30 18:17:41 INFO Loading plugin: amavisd_message_size_limit
2015-06-30 18:17:41 INFO Loading plugin: amavisd_wblist
2015-06-30 18:17:41 INFO Loading plugin: sql_alias_access_policy
2015-07-01 06:51:06 INFO Starting iRedAPD (version: 1.6.0, backend: mysql), listening on 127.0.0.1:7777.
2015-07-01 06:51:06 INFO Loading plugin: reject_null_sender
2015-07-01 06:51:06 INFO Loading plugin: amavisd_message_size_limit
2015-07-01 06:51:06 INFO Loading plugin: amavisd_wblist
2015-07-01 06:51:06 INFO Loading plugin: sql_alias_access_policy
2015-07-01 06:52:27 INFO Starting iRedAPD (version: 1.6.0, backend: mysql), listening on 127.0.0.1:7777.
2015-07-01 06:52:27 INFO Loading plugin: reject_null_sender
2015-07-01 06:52:27 INFO Loading plugin: amavisd_message_size_limit
2015-07-01 06:52:27 INFO Loading plugin: amavisd_wblist
2015-07-01 06:52:27 INFO Loading plugin: sql_alias_access_policy


# /etc/init.d/iredapd start
Starting iredapd ...


# tail -30 /var/log/iredapd.log
2015-06-30 18:01:18 INFO Starting iRedAPD (version: 1.6.0, backend: mysql), listening on 127.0.0.1:7777.
2015-06-30 18:01:18 INFO Loading plugin: reject_null_sender
2015-06-30 18:01:18 INFO Loading plugin: amavisd_message_size_limit
2015-06-30 18:01:18 INFO Loading plugin: amavisd_wblist
2015-06-30 18:01:18 INFO Loading plugin: sql_alias_access_policy
2015-06-30 18:01:58 INFO Starting iRedAPD (version: 1.6.0, backend: mysql), listening on 127.0.0.1:7777.
2015-06-30 18:01:58 INFO Loading plugin: reject_null_sender
2015-06-30 18:01:58 INFO Loading plugin: amavisd_message_size_limit
2015-06-30 18:01:58 INFO Loading plugin: amavisd_wblist
2015-06-30 18:01:58 INFO Loading plugin: sql_alias_access_policy
2015-06-30 18:17:41 INFO Starting iRedAPD (version: 1.6.0, backend: mysql), listening on 127.0.0.1:7777.
2015-06-30 18:17:41 INFO Loading plugin: reject_null_sender
2015-06-30 18:17:41 INFO Loading plugin: amavisd_message_size_limit
2015-06-30 18:17:41 INFO Loading plugin: amavisd_wblist
2015-06-30 18:17:41 INFO Loading plugin: sql_alias_access_policy
2015-07-01 06:51:06 INFO Starting iRedAPD (version: 1.6.0, backend: mysql), listening on 127.0.0.1:7777.
2015-07-01 06:51:06 INFO Loading plugin: reject_null_sender
2015-07-01 06:51:06 INFO Loading plugin: amavisd_message_size_limit
2015-07-01 06:51:06 INFO Loading plugin: amavisd_wblist
2015-07-01 06:51:06 INFO Loading plugin: sql_alias_access_policy
2015-07-01 06:52:27 INFO Starting iRedAPD (version: 1.6.0, backend: mysql), listening on 127.0.0.1:7777.
2015-07-01 06:52:27 INFO Loading plugin: reject_null_sender
2015-07-01 06:52:27 INFO Loading plugin: amavisd_message_size_limit
2015-07-01 06:52:27 INFO Loading plugin: amavisd_wblist
2015-07-01 06:52:27 INFO Loading plugin: sql_alias_access_policy
2015-07-01 07:15:14 INFO Starting iRedAPD (version: 1.6.0, backend: mysql), listening on 127.0.0.1:7777.
2015-07-01 07:15:14 INFO Loading plugin: reject_null_sender
2015-07-01 07:15:14 INFO Loading plugin: amavisd_message_size_limit
2015-07-01 07:15:14 INFO Loading plugin: amavisd_wblist
2015-07-01 07:15:14 INFO Loading plugin: sql_alias_access_policy

6 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,770

Re: CentOS 6.x uwsgi post 502 bad gateway daemonize commented out not send

iRedAPD was executed as root first, then switching to iRedAPD as daemon user, file owner and permission on settings.pyc is ok.

Could you please turn on debug mode in iRedAPD, restart it, and keep monitoring its log file, extract error message and paste here?
Reference: http://www.iredmail.org/docs/debug.iredapd.html

7 Reply by pbf343

  • pbf343
  • Member
  • Offline
  • Registered: 2013-05-30
  • Posts: 243

Re: CentOS 6.x uwsgi post 502 bad gateway daemonize commented out not send

ZhangHuangbin wrote:

iRedAPD was executed as root first, then switching to iRedAPD as daemon user, file owner and permission on settings.pyc is ok.

Could you please turn on debug mode in iRedAPD, restart it, and keep monitoring its log file, extract error message and paste here?
Reference: http://www.iredmail.org/docs/debug.iredapd.html

So are you in fact saying that because the service was started by the root user, that the compiled file is then owned by the root user.  Otherwise, the file would have been compiled via the daemon and thus owned by such?   


Yes, will do such but I must say that so far I've been unable to obtain any data as this is a new install.

8 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,770

Re: CentOS 6.x uwsgi post 502 bad gateway daemonize commented out not send

Excuse me, what do you mean "unable to obtain any data"?

9 Reply by pbf343

  • pbf343
  • Member
  • Offline
  • Registered: 2013-05-30
  • Posts: 243

Re: CentOS 6.x uwsgi post 502 bad gateway daemonize commented out not send

ZhangHuangbin wrote:

Excuse me, what do you mean "unable to obtain any data"?

Just that it is a new build not running long and no real users at this time.  So, I would think that "data" would be limited to starts, stops, errors, info, etc. but nothing like seen on live systems with mail passing, etc.

10 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,770

Re: CentOS 6.x uwsgi post 502 bad gateway daemonize commented out not send

The question is: is iRedAPD service now running? If it's running, you are able to send/receive email.

11 Reply by pbf343

  • pbf343
  • Member
  • Offline
  • Registered: 2013-05-30
  • Posts: 243

Re: CentOS 6.x uwsgi post 502 bad gateway daemonize commented out not send

ZhangHuangbin wrote:

The question is: is iRedAPD service now running? If it's running, you are able to send/receive email.

Yes, if the iredapd service is running, it will send e-mail.  However, the service does NOT start with reboots, etc. even though it is indicated to do such.  Thus, part of logic for file ownership, etc. and who is controlling the service.

Should there be a uwsgi log in /var/logs/?   Could that be part of issue?

12 Reply by pbf343

  • pbf343
  • Member
  • Offline
  • Registered: 2013-05-30
  • Posts: 243

Re: CentOS 6.x uwsgi post 502 bad gateway daemonize commented out not send

Some log data as requested.

2015-07-01 13:03:37 DEBUG Connect from 127.0.0.1, port 42225.
2015-07-01 13:03:37 DEBUG smtp session: request=smtpd_access_policy
2015-07-01 13:03:37 DEBUG smtp session: protocol_state=RCPT
2015-07-01 13:03:37 DEBUG smtp session: protocol_name=ESMTP
2015-07-01 13:03:37 DEBUG smtp session: client_address=127.0.0.1
2015-07-01 13:03:37 DEBUG smtp session: client_name=mail.domain.name
2015-07-01 13:03:37 DEBUG smtp session: reverse_client_name=mail.domain.name
2015-07-01 13:03:37 DEBUG smtp session: helo_name=_
2015-07-01 13:03:37 DEBUG smtp session: sender=postmaster@domain.name
2015-07-01 13:03:37 DEBUG smtp session: recipient=some.user.account@gmail.com
2015-07-01 13:03:37 DEBUG smtp session: recipient_count=0
2015-07-01 13:03:37 DEBUG smtp session: queue_id=
2015-07-01 13:03:37 DEBUG smtp session: instance=88b.55941d69.29f19.0
2015-07-01 13:03:37 DEBUG smtp session: size=0
2015-07-01 13:03:37 DEBUG smtp session: etrn_domain=
2015-07-01 13:03:37 DEBUG smtp session: stress=
2015-07-01 13:03:37 DEBUG smtp session: sasl_method=LOGIN
2015-07-01 13:03:37 DEBUG smtp session: sasl_username=postmaster@domain.name
2015-07-01 13:03:37 DEBUG smtp session: sasl_sender=
2015-07-01 13:03:37 DEBUG smtp session: ccert_subject=
2015-07-01 13:03:37 DEBUG smtp session: ccert_issuer=
2015-07-01 13:03:37 DEBUG smtp session: ccert_fingerprint=
2015-07-01 13:03:37 DEBUG smtp session: ccert_pubkey_fingerprint=
2015-07-01 13:03:37 DEBUG smtp session: encryption_protocol=TLSv1
2015-07-01 13:03:37 DEBUG smtp session: encryption_cipher=ECDHE-RSA-AES256-SHA
2015-07-01 13:03:37 DEBUG smtp session: encryption_keysize=256
2015-07-01 13:03:37 DEBUG --> Apply plugin: reject_null_sender
2015-07-01 13:03:37 DEBUG <-- Result: DUNNO
2015-07-01 13:03:37 DEBUG Skip plugin: amavisd_message_size_limit (protocol_state != RCPT)
2015-07-01 13:03:37 DEBUG --> Apply plugin: amavisd_wblist
2015-07-01 13:03:37 DEBUG Possible policy senders: ['@.', 'postmaster@domain.name', '@domain.name', '@.domain.name', '@name', '@.name', '127.0.0.1', '127.*.0.1', '127.*.*.*', '*.*.*.1', '127.0.0.*', '*.*.0.1', '*.0.0.1', '127.0.*.1', '*.*.*.*', '127.*.*.1', '127.0.*.*']
2015-07-01 13:03:37 DEBUG Possible policy recipients: ['@.', 'some.user.account@gmail.com', '@gmail.com', '@.gmail.com', '@com', '@.com', 'some.user.account@*']
2015-07-01 13:03:37 DEBUG SQL: Get policy senders: SELECT id,email FROM mailaddr WHERE email IN ('@.', 'postmaster@domain.name', '@domain.name', '@.domain.name', '@name', '@.name', '127.0.0.1', '127.*.0.1', '127.*.*.*', '*.*.*.1', '127.0.0.*', '*.*.0.1', '*.0.0.1', '127.0.*.1', '*.*.*.*', '127.*.*.1', '127.0.*.*') ORDER BY priority DESC
2015-07-01 13:03:37 DEBUG No senders found in SQL database.
2015-07-01 13:03:37 DEBUG <-- Result: DUNNO
2015-07-01 13:03:37 DEBUG --> Apply plugin: sql_alias_access_policy
2015-07-01 13:03:37 DEBUG SQL: query access policy: SELECT accesspolicy, goto, moderators
            FROM alias
            WHERE
                address='some.user.account@gmail.com'
                AND address <> goto
                AND active=1
            LIMIT 1
   

2015-07-01 13:03:37 DEBUG SQL: record: None
2015-07-01 13:03:37 DEBUG <-- Result: DUNNO (Not a mail alias account)
2015-07-01 13:03:37 INFO [127.0.0.1] RCPT, postmaster@domain.name -> some.user.account@gmail.com, DUNNO
2015-07-01 13:03:37 DEBUG Session ended
2015-07-01 13:03:37 DEBUG smtp session: request=smtpd_access_policy
2015-07-01 13:03:37 DEBUG smtp session: protocol_state=END-OF-MESSAGE
2015-07-01 13:03:37 DEBUG smtp session: protocol_name=ESMTP
2015-07-01 13:03:37 DEBUG smtp session: client_address=127.0.0.1
2015-07-01 13:03:37 DEBUG smtp session: client_name=mail.host.name.tld
2015-07-01 13:03:37 DEBUG smtp session: reverse_client_name=mail.host.name.tld
2015-07-01 13:03:37 DEBUG smtp session: helo_name=_
2015-07-01 13:03:37 DEBUG smtp session: sender=postmaster@domain.name
2015-07-01 13:03:37 DEBUG smtp session: recipient=some.user.account@gmail.com
2015-07-01 13:03:37 DEBUG smtp session: recipient_count=1
2015-07-01 13:03:37 DEBUG smtp session: queue_id=641B441DF14
2015-07-01 13:03:37 DEBUG smtp session: instance=88b.55941d69.29f19.0
2015-07-01 13:03:37 DEBUG smtp session: size=370
2015-07-01 13:03:37 DEBUG smtp session: etrn_domain=
2015-07-01 13:03:37 DEBUG smtp session: stress=
2015-07-01 13:03:37 DEBUG smtp session: sasl_method=LOGIN
2015-07-01 13:03:37 DEBUG smtp session: sasl_username=postmaster@domain.name
2015-07-01 13:03:37 DEBUG smtp session: sasl_sender=
2015-07-01 13:03:37 DEBUG smtp session: ccert_subject=
2015-07-01 13:03:37 DEBUG smtp session: ccert_issuer=
2015-07-01 13:03:37 DEBUG smtp session: ccert_fingerprint=
2015-07-01 13:03:37 DEBUG smtp session: ccert_pubkey_fingerprint=
2015-07-01 13:03:37 DEBUG smtp session: encryption_protocol=TLSv1
2015-07-01 13:03:37 DEBUG smtp session: encryption_cipher=ECDHE-RSA-AES256-SHA
2015-07-01 13:03:37 DEBUG smtp session: encryption_keysize=256
2015-07-01 13:03:37 DEBUG Skip plugin: reject_null_sender (protocol_state != END-OF-MESSAGE)
2015-07-01 13:03:37 DEBUG --> Apply plugin: amavisd_message_size_limit
2015-07-01 13:03:37 DEBUG Message size: 370
2015-07-01 13:03:37 DEBUG Getting applicable policies
2015-07-01 13:03:37 DEBUG Valid policy accounts for recipient some.user.account@gmail.com: 'some.user.account@gmail.com', '@gmail.com', '@.gmail.com', '@.'
2015-07-01 13:03:37 DEBUG SELECT policy_name,message_size_limit
                 FROM users, policy
                 WHERE
                    (users.policy_id=policy.id)
                    AND (users.email IN ('some.user.account@gmail.com', '@gmail.com', '@.gmail.com', '@.'))
                 ORDER BY users.priority DESC
                 
2015-07-01 13:03:37 DEBUG No policy found.
2015-07-01 13:03:37 DEBUG <-- Result: DUNNO
2015-07-01 13:03:37 DEBUG Skip plugin: amavisd_wblist (protocol_state != END-OF-MESSAGE)
2015-07-01 13:03:37 DEBUG Skip plugin: sql_alias_access_policy (protocol_state != END-OF-MESSAGE)
2015-07-01 13:03:37 INFO [127.0.0.1] END-OF-MESSAGE, postmaster@domain.name -> some.user.account@gmail.com, DUNNO
2015-07-01 13:03:37 DEBUG Session ended

13 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,770

Re: CentOS 6.x uwsgi post 502 bad gateway daemonize commented out not send

pbf343 wrote:

Should there be a uwsgi log in /var/logs/?   Could that be part of issue?

You can specify the log file path in /etc/uwsgi.ini:

daemonize = /var/log/uwsgi.log

14 Reply by pbf343 (edited by pbf343 2015-07-04 20:31:25)

  • pbf343
  • Member
  • Offline
  • Registered: 2013-05-30
  • Posts: 243

Re: CentOS 6.x uwsgi post 502 bad gateway daemonize commented out not send

ZhangHuangbin wrote:
pbf343 wrote:

Should there be a uwsgi log in /var/logs/?   Could that be part of issue?

You can specify the log file path in /etc/uwsgi.ini:

daemonize = /var/log/uwsgi.log

Would this be the CAUSE of it not starting at boot even though it is set to start?

Additionally, in this thread your response was to comment out the daemonize value.
http://www.iredmail.org/forum/topic9459 … inpro.html

So if I create:
   /var/log/uwsgi/
   /var/log/uwsgi/uwsgi.log
Whom should own these and what permissions?

Is any log rotate operation written/configured for this?

15 Reply by pbf343 (edited by pbf343 2015-07-04 21:13:47)

  • pbf343
  • Member
  • Offline
  • Registered: 2013-05-30
  • Posts: 243

Re: CentOS 6.x uwsgi post 502 bad gateway daemonize commented out not send

Information for everyone to see. 

daemonize active in uwsgi.ini file

mkdir /var/log/uwsgi/
touch /var/log/uwsgi/uwsgi.log
chmod 0640 /var/log/uwsgi/uwsgi.log


REBOOT of the system. 

service iredapd status
iredapd is running.

tail /var/log/uwsgi/uwsgi.log
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 145536 bytes (142 KB) for 1 cores
*** Operational MODE: single process ***
*** no app loaded. going in full dynamic mode ***
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 1980)
Sat Jul  4 08:39:01 2015 - [emperor] vassal iredadmin.ini has been spawned
spawned uWSGI worker 1 (pid: 1990, cores: 1)
Sat Jul  4 08:39:01 2015 - [emperor] vassal iredadmin.ini is ready to accept requests


NOTE:
    Left the uwsgi log dir and file owned by root at present. 

TO ANSWER:
    Should uwsgi dir or uwsgi.log be owned by ireadmin, or in future plans of such? 
    Are the permissions below accurate?


drwxr-xr-x   2 root        root          22 Jul  4 08:21 uwsgi
-rw-r-----   1 root root 3.7K Jul  4 08:39 uwsgi.log