Zammad ticketing/helpdesk on Nethserver available

Feature
41

Installed zammad on a semi production NS7 with Nextcloud, OnlyOffice and Elasticsearch. No issues at all, all functioning properly!

Spoke a bit too soon.

Zammad gives me an error: StatusCode 500

{“error”:“Unable to process GET request to elasticsearch URL ‘http://127.0.0.1:9200/zammad_production/Ticket/_search’. Elasticsearch is not reachable, probably because it’s not running or even installed.\n\nResponse:\n#\u003cUserAgent::Result:0x00007f25ec4739e8 @success=false, @body=nil, @data=nil, @code=0, @content_type=nil, @error="#\u003cErrno::ECONNREFUSED: Failed to open TCP connection to 127.0.0.1:9200 (Connection refused - connect(2) for \"127.0.0.1\" port 9200)\u003e"\u003e\n\nPayload:\n{:query=\u003e{:bool=\u003e{:must=\u003e[{:range=\u003e{"created_at"=\u003e{:from=\u003e"2019-01-01", :to=\u003e"2019-12-31"}}}], :must_not=\u003e[{:term=\u003e{"state"=\u003e"merged"}}]}}, :size=\u003e0, :aggs=\u003e{:time_buckets=\u003e{:date_histogram=\u003e{:field=\u003e"created_at", :interval=\u003e"month"}}}}\n\nPayload size: 0M”}

To reproduce: Log in as admin or user and click ‘Reporting’ ( lower left corner, right of the user profile)

I rebooted the server after installing zammad, but I’m not sure if the error was present before.

“systemctl status elasticsearch” shows that it IS running and elasticsearch in Nextcloud is working properly.

HTH

1 Like
42

I can not reproduce the error except of when I stop elasticsearch. Did you edit /etc/elasticsearch/elasticsearch.yml ?

Which other packages are installed?

rpm -qa "nethserver-*" | sort

Just to compare the elasticsearch output:

[root@testserver ~]# curl -X GET localhost:9200
{
  "name" : "miqcSTK",
  "cluster_name" : "elasticsearch",
  "cluster_uuid" : "90cgbWNtTx2WqAvPoDro9A",
  "version" : {
    "number" : "5.6.15",
    "build_hash" : "fe7575a",
    "build_date" : "2019-02-13T16:21:45.880Z",
    "build_snapshot" : false,
    "lucene_version" : "6.6.1"
  },
  "tagline" : "You Know, for Search"
}

I am going to test some more when updating the module…

43

As a follow up, some issues have been manually corrected. Awaiting the next test version for further testing.

1 Like
44

Update available!

  • zammad.conf - servername fixed
  • templated nginx zammad.conf
  • change port from 3000 to 3001 to safely coexist with ntopng
  • integrated to network services
  • app button
  • backup postgres db

Fresh install:

yum -y install https://mrmarkuz.goip.de/mirror/mrmarkuz/7/noarch/nethserver-mrmarkuz-0.0.1-3.ns7.noarch.rpm
yum -y install nethserver-zammad
config setprop zammad VirtualHost myserver.domain.local
yum -y install zammad
signal-event nethserver-zammad-update

Update:

yum -y update nethserver-zammad

2 Likes
45

Updated the initial install. All issues gone! Verified various config files and all ok.:slight_smile:

Your ‘trick’ by using the db key value of the virtual host for the app button should be integrated into all apps. Most of them (if not all) are hardcoded I guess.

Many thanks again!

2 Likes
46

Thanks again for testing!

I copied it from nethserver-mattermost.
With a virtualhost a db value is used.
In most other cases the browser url host is used and just “/appname” appended.

2 Likes
47

One more thing… :wink:

If I disable (config setprop zammad status disabled) zammad followed by signal-event nethserver-zammad-update, the httpd zammad.conf is still in place, where I would expect it to be removed.

After the above, and manually removing the zammad.conf file, the signal-event re-generates the zammad.conf file.

Would it be more consistent to have the signal-event check the status and thus will or will not generate the zammad.conf file?

Visiting the zammad virtualhost (e.g. zammad.myserver.com) now leads to and error message when zammad is set to disabled.

HTH

1 Like
48

Yes it would so I updated the module.
The zammad.conf is still generated as it’s a template but it gets emptied now when zammad is disabled.
Visiting the zammad virtualhost now shows the Nethserver page.

I added a Zammad wiki page.

1 Like
49

I’ve updated the module and can confirm the zammad.conf file is now ‘empty’ when status is set to disabled.

Again, many thanks. It now appears to be a very robust module.

1 Like
50

You’re welcome, thanks for testing.

@mandcsharma, seems the module is ready. :grinning:

3 Likes
51

Ehy guys! Great job. Wow a lot of testing and code here.
As we said at the conference in bruxelles in our community people ask things and most likely they get it
Kudos @mrmarkuz and @LayLow

23-Great-Job-Memes-16-720x480.jpg720×480 41.8 KB

2 Likes
52

Bravo guys, great job as usual :clap::clap::clap:

2 Likes
53

I found out that Zammad has a backup/restore script usable for cron so I updated the module.

  • Integrated daily backup cron jobsaves db and files for 10 days
  • Fixed restore-data procedure
  • Tested both (Nethserver and Zammad) backup/restore methods

This way we have another file/db backup if something goes wrong.

3 Likes
54

I can verify that all works fine!

Thanks.

2 Likes
55

Tested the Telegram integration option. Works like a charm. Inbound Telegram messages get delivered within seconds to Zammad and replies from Zammad to Telegram the same. Very cool!

https://zammad-admin-documentation.readthedocs.io/en/latest/channels-telegram.html

2 Likes
56

Kudos Markus, Zammad works brilliantly. Even better than I expected. :clap::clap::clap::clap::clap:

1 Like
57

FYI: https://community.zammad.org/t/zammad-3-1-is-there/2781

1 Like
58

Happy to see such projects improving and growing

1 Like
59

@mrmarkuz,

Is the wiki and packages from your repo up to par with latest elasticsearch (6 or 7) and Zammad 3.x series please?

I want to perform a new installation, and would like to use the latest :slight_smile:
TIA!!

1 Like
60

Zammad should always be the latest version, 3.1 actually.
Elasticsearch version 5.6.15 is used and supported, see Zammad docs. Do you think we should try a newer version?

1 Like