DNS does not work Bind problem...

[fearworks]

It has been marked as pending for 2 days...

---

Code:

################################################################
# Apache VHOST configuration file
# Automatically generated by Sentora 1.0.3
# Generated on: 19:01 29th Jun 2019 CEST
#==== YOU MUST NOT EDIT THIS FILE : IT WILL BE OVERWRITTEN ====
# Use Sentora Menu -> Admin -> Module Admin -> Apache config
################################################################

Listen 80

# Configuration for Sentora control panel.
<VirtualHost *:80>
ServerAdmin zadmin@localhost
DocumentRoot "/etc/sentora/panel/"
ServerName panel.next-station.fr
ErrorLog "/var/sentora/logs/sentora-error.log"
CustomLog "/var/sentora/logs/sentora-access.log" combined
CustomLog "/var/sentora/logs/sentora-bandwidth.log" common
AddType application/x-httpd-php .php
<Directory "/etc/sentora/panel/">
Options +FollowSymLinks -Indexes
   AllowOverride All
   Require all granted
</Directory>

# Custom settings are loaded below this line (if any exist)

</VirtualHost>

################################################################
# Sentora generated VHOST configurations below.....
################################################################

My domain name has been waiting for two days on Sentora  ...

Ah OK, that looks more like an issue with the Sentora daemon not running.

If you log into Sentora, go to Admin -> Sentora Config and scroll to the bottom, what does the Sentora Daemon section show?

It should look something like this:

Sentora Daemon

Next Daemon Run:  15:15 30th Jun 2019 BST
Last Daemon Run:  15:10 30th Jun 2019 BST
Last Day Daemon Run:  15:15 29th Jun 2019 BST
Last Week Daemon Run:  14:00 28th Jun 2019 BST
Last Month Daemon Run:  13:50 29th Jun 2019 BST

Keith

[Greval]

Sentora does not generate in the file...

---

It looks like this, actually.

---

I have :
Sentora Daemon
Next Daemon Run: 19:06 29th Jun 2019 CEST
Last Daemon Run: 19:01 29th Jun 2019 CEST
Last Day Daemon Run: 19:01 29th Jun 2019 CEST
Last Week Daemon Run: 19:01 29th Jun 2019 CEST
Last Month Daemon Run: 19:01 29th Jun 2019 CEST

[fearworks]

Sentora does not generate in the file...

---

It looks like this, actually.

---

I have :
Sentora Daemon
Next Daemon Run: 19:06 29th Jun 2019 CEST
Last Daemon Run: 19:01 29th Jun 2019 CEST
Last Day Daemon Run: 19:01 29th Jun 2019 CEST
Last Week Daemon Run: 19:01 29th Jun 2019 CEST
Last Month Daemon Run: 19:01 29th Jun 2019 CEST

Is it updating the "Next Daemon Run" date every five minutes or did you have to press the "Go" button for the "Queue a full daemon run (reset)" option to get those dates generated?

I think you should have a read through this thread, starting from the post I have linked to (because I don't think the first few posts are relevant to you) and follow the advice about checking the daemon is running, and checking the crontab, etc.:

http://forums.sentora.org/showthread.php...4#pid19314

I suspect that the cron is working correctly and that there's an error being generated when the daemon tries to run, so it crashes out and doesn't run properly, but you should see this by looking at the daemon run log (again, one of the posts in the above thread explains this).

Let me know once you've had a good read through and tried out the suggestions - obviously "cherry-pick" the suggestions that seem relevant and, where the discussion is about other problems, read past them

Keith.

[Greval]

Cron wasn't installed, is that normal?

---

After the installation of Cron everything works!

Thank you for your help! Soon Sentora should install Cron automatically during the installation! Thank you for your help

[fearworks]

Cron wasn't installed, is that normal?

---

After the installation of Cron everything works!

Thank you for your help! Soon Sentora should install Cron automatically during the installation! Thank you for your help

Cron should be installed with Sentora, but perhaps there is an issue with the installation script running on Ubuntu - I don't know, I use CentOS but maybe someone else could comment? The fact that you appear to have installed Sentora more than once and this has happened each time is a bit worrying...

It might also be worth manually going through the cron section of the installation script you used (probably this one? -> https://raw.githubusercontent.com/sentor...install.sh) and just making sure your late installation of cron is caught up with everything and no essential steps have been missed out.

Keith.

[Greval]

I reinstalled everything, don't worry! And indeed this is a problem for Ubuntu users.

Have a good day!

[TGates]

Interesting, this is why I always have used Ubuntu since the installer has worked just fine for me every time. (On VMs and on actual servers.) Maybe the Ubuntu repository its self has changed recently.

[fearworks]

Interesting, this is why I always have used Ubuntu since the installer has worked just fine for me every time. (On VMs and on actual servers.) Maybe the Ubuntu repository its self has changed recently.

I might try a test Ubuntu VM and see if I can see any obvious issues... I think it was Ubuntu 14.04.

Keith