Installation error on Centos 8

[Meth]

When installing to Centos 8, all the steps are completed, but I get an error at the API access connection stage. When I look at the rawlog, I don't see a clear result.


Rawlog;

EXITCODE=0
Leave it
spawn ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ro...@10.2.40.140 sudo chown apache /etc/bacularis/API/bacularis.users
Failed to create directory '/var/www/.ssh'.
Warning: Permanently added '10.2.40.140' (ECDSA) to the list of known hosts.
Password for ro...@10.2.40.140:
Connection 10.2.40.140 is closed.


EXITCODE=0
Leave it
spawn ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ro...@10.2.40.140 sudo chmod 600 /etc/bacularis/API/bacularis.users
Failed to create directory '/var/www/.ssh'.
Warning: Permanently added '10.2.40.140' (ECDSA) to the list of known hosts.
ro...@10.2.40.140 password:10.2.40.140 connection closed.


EXITCODE=0
Leave it
===== Step: Set Bacularis password =====

spawn scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null /usr/share/bacularis/protected/Web/Config/bacularis.users_new ro...@10.2.40.140:/tmp/bacularis-deploy/bacularis.users_new
Failed to create directory '/var/www/.ssh'.
Warning: Permanently added '10.2.40.140' (ECDSA) to the list of known hosts.
Password for ro...@10.2.40.140:

bacularis.users_new 0% 0 0.0KB/s --:-- ETAbacularis.users_new 100% 44 47.5KB/s 00:00    

EXITCODE=0
Leave it
spawn ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ro...@10.2.40.140 sudo mv /tmp/bacularis-deploy/bacularis.users_new /etc/bacularis/Web/bacularis.users
Failed to create directory '/var/www/.ssh'.
Warning: Permanently added '10.2.40.140' (ECDSA) to the list of known hosts.
Password for ro...@10.2.40.140:
Connection 10.2.40.140 is closed.


EXITCODE=0
Leave it
spawn ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ro...@10.2.40.140 sudo chown apache /etc/bacularis/Web/bacularis.users
Failed to create directory '/var/www/.ssh'.
Warning: Permanently added '10.2.40.140' (ECDSA) to the list of known hosts.
ro...@10.2.40.140 password:10.2.40.140 connection closed.


EXITCODE=0
Leave it
spawn ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ro...@10.2.40.140 sudo chmod 600 /etc/bacularis/Web/bacularis.users
Failed to create directory '/var/www/.ssh'.
Warning: Permanently added '10.2.40.140' (ECDSA) to the list of known hosts.
Password for ro...@10.2.40.140:
Connection 10.2.40.140 is closed.


EXITCODE=0
Leave it
===== Step Start Bacularis =====

spawn ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ro...@10.2.40.140 sudo systemctl start nginx 2>&1
Failed to create directory '/var/www/.ssh'.
Warning: Permanently added '10.2.40.140' (ECDSA) to the list of known hosts.

Password for ro...@10.2.40.140:
Connection 10.2.40.140 is closed.


EXITCODE=0



netstat output;

[Marcin Haba]

Hi Meth,

Thanks for reporting this problem. I remember that in the past you already experienced this issue.

Today I spent a couple of hours to find why it happens and I couldn't find any reason. Everything seems to be correct. Also I tried to reproduce it on CentOS 8 but without success. For now I can't say anything sure.

I am planning to look at it once again after the weekend. Until this time I have few questions for that:

1) why in the deployment output you have a phrase "Leave it" while there should be "quit"? Bacularis does not produce in output any "Leave it" string in this place. Are you using any translator or plugin in the web browser?

2) The last line of this output is:

EXITCODE=0

Was there a "quit" word after the last EXITOCDE=0 which was not pasted to e-mail or it is all complete output?

3) is there any reason that you use sudo option for the root user? Normally root does not need sudo in this deployment window.

4) does this problem with failed last deployment step happen always or only from time to time or with specific operating systems?

Thanks in advance for providing these details and for your help.

Best regards,
Marcin Haba (gani)

--
You received this message because you are subscribed to the Google Groups "bacularis" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bacularis+...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/bacularis/51571044-c4d3-4f99-9a31-3f08411e9c9en%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Meth]

Hello Marcin.

The answer to question 1 was because of the Translate application I used for a clear expression. Sorry for that.

2.quit was only there, I did not copy it.

The 3rd answer was actually I chose sudo because it was a habit.

The 4th answer was only this one, but I solved the problem.

I got this error because of the PHP-FPM version. I had 8.3 in the system before, but the version was conflicting because Bacularis version 7.4 was automatically installed, so I configured it to work with Bacularis 8.3.

8 Kasım 2024 Cuma tarihinde saat 19:03:03 UTC+3 itibarıyla Marcin Haba şunları yazdı:

[Marcin Haba]

Hi Meth,

Thanks for your answers to questions.

If changing php-fpm solved this issue that is great. I don't know why the newer PHP version causes this error to stop occurring, but I don't need to understand it :-) THe most important thing is that it started working on your side.

Best regards,
Marcin Haba (gani)

To view this discussion, visit https://groups.google.com/d/msgid/bacularis/3d80a9b2-b660-4a8d-8825-f4a30532c15dn%40googlegroups.com.

[Marcin Haba]

Hi Meth,

Could you tell me if on this host 10.2.41.218 there exists this directory:

/tmp/bacularis-deploy/

if yes, could you show me its content by:

ls -la /tmp/bacularis-deploy/

I don't know yet what causes this failed last step, but I would like to know if in the above directory you have something.

I also have a question if you tried the same deployment on a different web browser (the best without any plugin installed) or in private/incognito window with disabled the web browser plugins?

Thanks!

Best regards,
Marcin Haba (gani)

On Wed, 13 Nov 2024 at 11:55, Meth <bys...@gmail.com> wrote:

Hello Marcin,

Again, I got the API Link red X error, but when I checked it manually, I was able to access the API Link. I experienced this a few more times after this incident.

This is the Rawout log output;

===== Step: Set Bacularis password ===== spawn scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null /usr/share/bacularis/protected/Web/Config/bacularis.users_new ro...@10.2.41.218:/tmp/bacularis-deploy/bacularis.users_new Could not create directory '/var/www/.ssh'. Warning: Permanently added '10.2.41.218' (ECDSA) to the list of known hosts. ro...@10.2.41.218's password: bacularis.users_new 0% 0 0.0KB/s --:-- ETA bacularis.users_new 100% 44 41.1KB/s 00:00 EXITCODE=0 quit spawn ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ro...@10.2.41.218 sudo mv /tmp/bacularis-deploy/bacularis.users_new /etc/bacularis/Web/bacularis.users Could not create directory '/var/www/.ssh'. Warning: Permanently added '10.2.41.218' (ECDSA) to the list of known hosts. ro...@10.2.41.218's password:Connection to 10.2.41.218 closed. EXITCODE=0 quit spawn ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ro...@10.2.41.218 sudo chown apache /etc/bacularis/Web/bacularis.users Could not create directory '/var/www/.ssh'. Warning: Permanently added '10.2.41.218' (ECDSA) to the list of known hosts. ro...@10.2.41.218's password: Connection to 10.2.41.218 closed. EXITCODE=0 quit spawn ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ro...@10.2.41.218 sudo chmod 600 /etc/bacularis/Web/bacularis.users Could not create directory '/var/www/.ssh'. Warning: Permanently added '10.2.41.218' (ECDSA) to the list of known hosts. ro...@10.2.41.218's password: Connection to 10.2.41.218 closed. EXITCODE=0 quit ===== Step: Start Bacularis ===== spawn ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ro...@10.2.41.218 sudo systemctl start nginx 2>&1 Could not create directory '/var/www/.ssh'. Warning: Permanently added '10.2.41.218' (ECDSA) to the list of known hosts. ro...@10.2.41.218's password: Connection to 10.2.41.218 closed. EXITCODE=0 quit

8 Kasım 2024 Cuma tarihinde saat 19:47:21 UTC+3 itibarıyla Marcin Haba şunları yazdı:

[Marcin Haba]

Hi Meth,

Don't worry because it is a good sign. This path should exist only on the deployment process. After it is removed. My question was to check if there is any leftover after the deployment. But it looks that there isn't any and that is good :-)

For the other web browser, yes, it might be good to check it. Thanks.

Best regards,
Marcin Haba (gani)

PS. Please don't forget to keep the user group e-mail in mail copy :-)

On Wed, 13 Nov 2024 at 12:41, Meth <bys...@gmail.com> wrote:

Unfortunately there is no such path :(

I haven't tried it in another browser, but I'll try it in another browser in the next installation and let you know.

root@bacula:/tmp# ls -la /tmp/bacularis-deploy/
ls: cannot access '/tmp/bacularis-deploy/': No such file or directory
root@bacula:/tmp#

Marcin Haba <gani...@gmail.com>, 13 Kas 2024 Çar, 14:37 tarihinde şunu yazdı: