A couple of days ago i tried this tool for a little project and it goes without errors for now, but the service looks inactive (exited) so this is what im doing actually.
Im using Centos 7 virtual machine on VMware and Zimbra open source 8.7.10. I read tutorials about setup zimbra, I make a dns name on the same virtual machine but Im not sure if this works good or I have to install another Centos for doing DNS server work.
I tested the DNS I made with Windows 8.1 (installed on my dektop machine) with nslookup adding ip on dns net properties and it got response.
I cant enter on Zimbra web console, maybe Im missing something.
[root#mail ~]# systemctl status zimbra
● zimbra.service - LSB: Zimbra mail service
Loaded: loaded (/etc/rc.d/init.d/zimbra; bad; vendor preset: disabled)
Active: active (exited) since vie 2017-06-30 11:43:34 -04; 19min ago
Docs: man:systemd-sysv-generator(8)
Process: 834 ExecStart=/etc/rc.d/init.d/zimbra start (code=exited,
status=0/SUCCESS)
jun 30 11:42:03 mail zimbra[834]: Starting opendkim...Done.
jun 30 11:42:03 mail zimbra[834]: Starting snmp...Done.
jun 30 11:42:05 mail zimbra[834]: Starting spell...Done.
jun 30 11:42:10 mail zimbra[834]: Starting mta...Done.
jun 30 11:42:12 mail zimbra[834]: Starting stats...Done.
jun 30 11:42:23 mail zimbra[834]: Starting service webapp...Done.
jun 30 11:42:29 mail zimbra[834]: Starting zimbra webapp...Done.
jun 30 11:42:30 mail zimbra[834]: Starting zimbraAdmin webapp...Done.
jun 30 11:42:30 mail zimbra[834]: Starting zimlet webapp...Done.
jun 30 11:43:35 mail systemd[1]: Started LSB: Zimbra mail service.
I hope you can help me, thank you in advance.
now i can use zimbra. The error were 2, the first one was allowing port 7071 on Server side, the other was the DNS config, this last one is just pointing to Zimbra IP in DNS field. Even i can send mails to gmail what i think it was impossible, jaja.
Anyway thank you, but if someone have a good practices for zimbra Im all ears. I mean certificates for tls/ssl for clients believe its safe.
Cheers!
Related
I just installed filebeat, logstash, kibana and elasticsearch all running smoothly just to trial this product out for additional monthly reports/monitoring and noticed every time I try to change the "/etc/elasticsearch/elasticsearch.yml" config file for remote web access it'll basically crash the service every time I make the change.
Just want to say I'm new to the forum and this product, and my end goal for this question is to figure out how to allow remote connections to access elastisearch as I guinea pig and test without crashing elasticsearch.
For reference here is the error code when I run the 'sudo systemctl status elasticsearch' query:
Dec 30 07:27:37 ubuntu systemd[1]: Starting Elasticsearch...
Dec 30 07:27:52 ubuntu systemd-entrypoint[4067]: ERROR: [1] bootstrap checks failed. You must address the points described in the following [1] lines before starting Elasticsearch.
Dec 30 07:27:52 ubuntu systemd-entrypoint[4067]: bootstrap check failure [1] of [1]: the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.se>
Dec 30 07:27:52 ubuntu systemd-entrypoint[4067]: ERROR: Elasticsearch did not exit normally - check the logs at /var/log/elasticsearch/elasticsearch.log
Dec 30 07:27:53 ubuntu systemd[1]: elasticsearch.service: Main process exited, code=exited, status=78/CONFIG
Dec 30 07:27:53 ubuntu systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
Dec 30 07:27:53 ubuntu systemd[1]: Failed to start Elasticsearch.
Any help on this is greatly appreciated!
So i m trying to install a jenkins server on the free instance provided by aws, so I can test things out, problem is that I can connect via ssh using putty to the public ip and my key, but when I try to access the jenkins portal using the public DNS address and the port a timeout is returned
Also if i try to ping the machine from my laptop it returns "Request time out" every time.
Also jenkins server seems to be running and active:
[ec2-user#ip-1235 ~]$ sudo systemctl status jenkins
● jenkins.service - LSB: Jenkins Automation Server
Loaded: loaded (/etc/rc.d/init.d/jenkins; bad; vendor preset: disabled)
Active: active (running) since Mon 2021-11-22 16:14:42 UTC; 7min ago
Docs: man:systemd-sysv-generator(8)
Process: 3693 ExecStart=/etc/rc.d/init.d/jenkins start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/jenkins.service
└─3697 /etc/alternatives/java -Djava.awt.headless=true -DJENKINS_H...
Nov 22 16:14:42 ip-1234.us-east-2.compute.internal systemd[1]: Start...
Nov 22 16:14:42 ip-1234.us-east-2.compute.internal jenkins[3693]: St...
Nov 22 16:14:42 ip-1234.us-east-2.compute.internal systemd[1]: Start...
Hint: Some lines were ellipsized, use -l to show in full.
I have installed lighttpdon my new CENOS 7.
When I'm trying to access my IP, it is loading than eventually says that the site can't be reached, (ERR_CONNECTION_TIMED_OUT).
WHen runnig systemctl status lighttpd -l, It looks like the service is up and running.
Any idea?
[root#myvps ~]# systemctl status lighttpd -l
● lighttpd.service - Lightning Fast Webserver With Light System Requirements
Loaded: loaded (/usr/lib/systemd/system/lighttpd.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2020-02-11 09:50:53 CET; 19min ago
Main PID: 7559 (lighttpd)
CGroup: /system.slice/lighttpd.service
└─7559 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
Feb 11 09:50:53 myvps.mydomain.net systemd[1]: Stopped Lightning Fast Webserver With Light System Requirements.
Feb 11 09:50:53 myvps.mydomain.net systemd[1]: Started Lightning Fast Webserver With Light System Requirements.
Feb 11 09:50:53 myvps.mydomain.net lighttpd[7559]: 2020-02-11 09:50:53: (network.c.162) warning: please use server.use-ipv6 only for hostnames, not without server.bind / empty address; your config will break if the kernel default for IPV6_V6ONLY changes
Feb 11 09:50:53 myvps.mydomain.net lighttpd[7559]: 2020-02-11 09:50:53: (server.c.1437) can't have more connections than fds/2: 1024 1024
[root#myvps ~]#
Solved by running
firewall-cmd --permanent --add-service=http
success
[root#myvps~]# firewall-cmd --reload
success
found it somewhere on the web.
I'm running Manjaro 18.1.0 and using the interception-caps2esc 0.1.3-2 plugin via AUR. My /etc/udevmon.yaml and /etc/systemd/system/udevmon.service are setup as described in the answer here. This has been working fine for months, but has now suddenly stopped working. I tried re-booting.
I'm quite stumped as to what's caused the difference. I notice, however, that running systemctl status udevmon.service returns
● udevmon.service - udevmon
Loaded: loaded (/etc/systemd/system/udevmon.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Sun 2019-10-13 16:34:06 CEST; 20min ago
Main PID: 7749 (code=dumped, signal=SEGV)
Oct 13 16:34:06 my-pc systemd[1]: Started udevmon.
Oct 13 16:34:06 my-pc systemd[1]: udevmon.service: Main process exited, code=dumped, status=11/SEGV
Oct 13 16:34:06 my-pc systemd[1]: udevmon.service: Failed with result 'core-dump'.
which I suppose is relevant. systemctl reset-failed does not help, and my understanding of systemd and the workings of caps2esc is too limited to identify relevant next steps for solving this problem or for troubleshooting.
My question: What steps can I take to resolve or further troubleshoot this issue?
I experienced the same issue and was able to resolve it by reinstalling interception-tools and interception-caps2esc (I'm using yay):
yay -S interception-tools
yay -S interception-caps2esc
And then restarting the udevmon service:
sudo systemctl restart udevmon.service
I can't explain why it broke or why this fixes it but it did for me.
I have 3 new fresh installs of Ubuntu 16.04.2 LTS xenial on Azure VM, in the system log I noticed I have a time discrepancy and the system is logging this ever 5 seconds.
Mar 5 17:57:57 server1 systemd[1]: snapd.refresh.timer: Adding 2h 17min 4.279485s random time.
Mar 5 17:57:57 server1 systemd[1]: apt-daily.timer: Adding 5h 14min 48.381690s random time.
Mar 5 17:57:57 server1 systemd[19425]: Time has been changed
Mar 5 17:57:57 server1 systemd[37054]: Time has been changed
I have stopped the two services: apt-daily.timer and snapd.refresh.timer, and the "Time has been changed" messages still persist. It seems to be a time discrepancy between the VM and host system. I am not sure how to address this. I also have VMs of the same exact version that I installed over a month ago on Azure and they don't show this error.
Thanks for guidance on this