-
Notifications
You must be signed in to change notification settings - Fork 725
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zammad on CentOS7 - after update zammad no working again! #1269
Comments
Hi Stephan, looks to me like something went wrong while performing the database migrations. Might be a duplicate of #1261. Could you please run Thanks! |
Hallo Thorsten, [root@zammad ~]# zammad run rake db:migrate == 20170525000002 FixedTwitterTicketArticlePreferences: migrating ============= == 20170529000002 SettingDeliveryPermanentFailed: migrating =================== == 20170529132120 LdapMultiGroupMapping: migrating ============================ == 20170531144425 ForeignKeys: migrating ====================================== == 20170608151442 EnhancedPermissions: migrating ============================== == 20170619000001 TreeSelect: migrating ======================================= == 20170626000001 LocaleAddDirection: migrating =============================== == 20170628000001 FormGroupSelection: migrating =============================== == 20170713000001 OmniauthOffice365Setting: migrating ========================= == 20170713000002 TicketZoomSetting2: migrating =============================== == 20170714000001 ObjectManagerUserEmailOptional: migrating =================== == 20170714000002 UserEmailMultipleUse: migrating ============================= == 20170714000003 CleanupCtiLog: migrating ==================================== Greetings |
I can't spot any errors on that except that they were not executed. Could you please retry using Zammad now? |
Hallo, GRRR.... greetings |
Can you please re-run |
I done so. the status is "running"... [root@zammad ~]# systemctl status zammad Jul 18 14:08:04 zammad systemd[1]: Stopping zammad.service... |
additional infos: [root@zammad ~]# systemctl status nginx [root@zammad ~]# netstat -tulpen |
Can you please provide the current content of the |
i attached it on first post as zammad.zip... |
Please note that this is not the newest version available. The last entry in the log has the timestamp |
ok, doing again... ;o) |
Thanks! That looks much better now. It looks so good, that there is no new error in there :) Could you please ensure to run the command |
one moment please... ;o) |
Hallo Thorsten, Greetings |
[root@zammad ~]# systemctl status zammad Jul 18 14:36:56 zammad systemd[1]: Started zammad.service. |
Only for information: 502 Bad Gateway Why it is so difficult to update zammad? |
For security reasons with Zammad 1.6 and higher we changed the bindings from 0.0.0.0:3000 - it's only bound on localhost:3000 now. So you can't connect through network to application server on port 3000 anymore. You have two possibilities:
To verify if this is your issue use "netstat -tan|grep 3000" |
Hallo Martin, But why change the nginx configuration? It makes no sense for me, to block external connect to a helpdesk. Who should work with a system, that isn't reachable over network? I try your docs now... Greetings |
Hallo Martin, If i try to use certificates is there a doc how to configure this with zammad and nginx? Greetings |
Hi Stephan,
The nginx config has not changed. It's still working if you use nginx on localhost and proxy app requests to localhost:3000. -Martin |
No. Application binding will keep on localhost. If you changed it via https://docs.zammad.org/en/latest/appendix-configure-env-vars.html#configure-ip then it is persistent (will keep on reboot and on Zammad update).
You can use certificates with nginx as usual with any other nginx setups. An example config is here https://github.com/zammad/zammad/blob/develop/contrib/nginx/zammad_ssl.conf but you also can search the internet for normal nginx+ssl howtos. Good look! 🤡 I'm sure you willing got to live nginx! 😁 |
PS: Your avatar is really good! 👍 |
Hallo Martin,
i will try to change to https with certificate on nginx.
notice you, how it works... ;o)
Greetings
Stephan, the ruebenmaster
Gesendet: Dienstag, 18. Juli 2017 um 15:22 Uhr
Von: "Martin Edenhofer" <notifications@github.com>
An: zammad/zammad <zammad@noreply.github.com>
Cc: ruebenmaster <ruebenmaster@web.de>, "State change" <state_change@noreply.github.com>
Betreff: Re: [zammad/zammad] zammad on CentOS7 - after update zammad no working again! (#1269)
PS: Your avatar is really good! 👍
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Wunderfull! |
JFI: Reopen if needed. Thanks a lot! |
Hallo People, Now i try to update my production server zammad. And what do i read? "Paket zammad-1.6.1-1500902763.dab9fe99.centos7.x86_64.rpm ist nicht unterschrieben" What is this? Is there a way to update the server without problems... It is very difficult now, to stopp my boss choosing another ticket system... Greetings |
Any ideas about that? It's RPM on centos7. @ruebenmaster We use https://packager.io for building packages. So we have basically no influence here. Anyway, I recommend to have a test system anyway. |
I have decide to install all new... But i have it installed correctly the way it is written on zammad.org. I don't know why there are a lot of problems with updating zammad on CentOS 7 and openSUSE 42.2. Maybe i have to use ubuntu. :O))) packager.io, please not more to configurate... :O) There is no time for more. greetings |
Ok, people... "Paket zammad-1.5.0-1500965473.2be861e2.centos7.x86_64.rpm ist nicht unterschrieben" anybody a idea? Sorry Martin, i haven't time for troubleshooting by new installation. greetings |
I'll try it by my self... I never have had issue here before. |
what should i say? Another question is, why is the version 1.5.0? on testing system we are at 1.6.1... ? |
1.) Seems to be packager.io related.
2.) Seems you used the develop packages before and now the stable packages. |
I can confirm that. @ruebenmaster you are right, with old repo file the "not signed" messages appears. With new repo file (as @monotek wrote) it's working fine. Just updating the documentation right now.... |
Hallo monotek, Greetings |
@monotek thanks PS: It's also needed here https://docs.zammad.org/en/latest/install-update.html#update-with-rpm and https://docs.zammad.org/en/latest/install-update.html#update-with-deb right? And centos7 has only curl on minimal installation (no wget). |
Thx. On real life it is under: i used /etc/nginx/conf.d/zammad.conf. right? Thanks for your help. Greetings |
@martine fixed in: zammad/zammad-documentation@03f4d9d |
Hello, Zammad is running on CentOS7 I tried to reach zammad from the ticket server machine and its still working. So i tried the above solution: zammad config:set ZAMMAD_BIND_IP=0.0.0.0 But the problem persists. Can someone help me to get it running again? greetings |
Port seems open so it could be an firewall issue. Nevertheless i suggest to not use 0.0.0.0 and configure nginx to proxy port 80 to port 3000 as it's more secure. Using 0.0.0.0 means https configuration could be bypassed. |
I checked the Firewall. Can't see anything. Everything seems to be allright. |
i got it. |
Yes, there is an example nginx config in: https://github.com/zammad/zammad/blob/develop/contrib/nginx/zammad.conf Should be enabled by default when you installed via deb or rpm package. |
Hallo people,
today i made an update because of security. I used a virtual machine on vmware 6. Linux distribution is CentOS7. ( yum update )
now it is the third time, zammad doesn't start after update to 1.6.1. the nginx don't show it anymore...
zammad.zip
The installed version is: 1.6.1-1500274100.a9a76ef.centos7
The installation was done exactly the howto on zammad.org. (where 1.5.0 is titeld as the newest version)
CentOS version: Linux version 3.10.0-514.26.2.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Tue Jul 4 15:04:05 UTC 2017
in attachment the production logfile... Now i try it on opensuse 42.2. if it fail too, zammad is dead for production use...
greetings
Stephan
The text was updated successfully, but these errors were encountered: