• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Fog service is not accessible after reboot

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    2
    4
    230
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • cidy.long 0C
      cidy.long 0
      last edited by

      • Rocky Linux 9 clean installed on x86_64 arch machine
      • installed lab-core from red-hat by [dnf --enablerepo=devel install redhat-lsb-core]
      • get most recently version (1.5.10) fog-project from GitHub by [git clone https://github.com/FOGProject/fogproject.git] yesterday.
      • Rocky Linux 9 config as:
        • Gateway (Route): 10.0.1.1
        • NIC config: static ip address: 10.0.1.120
      • Here are the settings FOG will use:
        • Base Linux: Redhat
        • Detected Linux Distribution: Rocky Linux
        • Interface: enp1s0
        • Server IP Address: 10.0.1.120
        • Server Subnet Mask: 255.255.255.0
        • Hostname: rocky9fog.tweedheadstorae.com.au
        • Installation Type: Normal Server
        • Internationalization: No
        • Image Storage Location: /images
        • Using FOG DHCP: Yes
        • DHCP router Address: 10.0.1.1
        • Send OS Name, OS Version, and FOG Version: Yes

      When installation, everything went smoothly to end to complete

      • Setup complete

        • You can now login to the FOG Management Portal using

        • the information listed below. The login information

        • is only if this is the first install.

        • This can be done by opening a web browser and going to:

        https://10.0.1.120/fog/management

        Default User Information
        Username: fog
        Password: password

        • Changed configurations:

          The FOG installer changed configuration files and created the
          following backup files from your original files:

          • /etc/dhcp/dhcpd.conf <=> /etc/dhcp/dhcpd.conf.1682897839
          • /etc/vsftpd/vsftpd.conf <=> /etc/vsftpd/vsftpd.conf.1682897839
          • /etc/exports <=> /etc/exports.1682897839

      Tried to access from above advised URL and successful

      This a snapshot for netstat to show apache listen on IPV6, but access by using IPV4 is okay.!

      [root@rocky9fog ~]# netstat -tunlp
      Active Internet connections (only servers)
      Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
      tcp 0 0 0.0.0.0:51101 0.0.0.0:* LISTEN 1306/rpc.statd
      tcp 0 0 0.0.0.0:46413 0.0.0.0:* LISTEN -
      tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 867/php-fpm: master
      tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 1307/vsftpd
      tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 868/sshd: /usr/sbin
      tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1/systemd
      tcp 0 0 0.0.0.0:20048 0.0.0.0:* LISTEN 1322/rpc.mountd
      tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN -
      tcp6 0 0 :::58315 :::* LISTEN 1306/rpc.statd
      tcp6 0 0 :::443 :::* LISTEN 10423/httpd
      tcp6 0 0 :::22 :::* LISTEN 868/sshd: /usr/sbin
      tcp6 0 0 :::111 :::* LISTEN 1/systemd
      tcp6 0 0 :::80 :::* LISTEN 10423/httpd
      tcp6 0 0 :::20048 :::* LISTEN 1322/rpc.mountd
      tcp6 0 0 :::40109 :::* LISTEN -
      tcp6 0 0 :::3306 :::* LISTEN 953/mariadbd
      tcp6 0 0 :::2049 :::* LISTEN -
      udp 0 0 0.0.0.0:42628 0.0.0.0:* 1306/rpc.statd
      udp 0 0 0.0.0.0:20048 0.0.0.0:* 1322/rpc.mountd
      udp 0 0 0.0.0.0:40828 0.0.0.0:* 1297/dhcpd
      udp 0 0 0.0.0.0:36880 0.0.0.0:* -
      udp 0 0 0.0.0.0:67 0.0.0.0:* 1297/dhcpd
      udp 0 0 0.0.0.0:111 0.0.0.0:* 1/systemd
      udp 0 0 127.0.0.1:323 0.0.0.0:* 816/chronyd
      udp 0 0 127.0.0.1:659 0.0.0.0:* 1306/rpc.statd
      udp6 0 0 :::54528 :::* 1297/dhcpd
      udp6 0 0 :::39064 :::* 1306/rpc.statd
      udp6 0 0 :::20048 :::* 1322/rpc.mountd
      udp6 0 0 :::36756 :::* -
      udp6 0 0 :::69 :::* 1/systemd
      udp6 0 0 :::111 :::* 1/systemd
      udp6 0 0 ::1:323 :::* 816/chronyd

      It is very confused.

      Reboot server and tried access https://10.0.1.120/fog/management, browser response:

      Unable to connect

      An error occurred during a connection to 10.0.1.120.

      The site could be temporarily unavailable or too busy. Try again in a few moments.
      If you are unable to load any pages, check your computer’s network connection.
      If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.
      

      tried to check the service status by

      [root@rocky9fog ~]# systemctl -l | grep FOG
      FOGImageReplicator.service loaded active running FOGImageReplicator
      FOGImageSize.service loaded active running FOGImageSize
      FOGMulticastManager.service loaded active running FOGMulticastManager
      FOGPingHosts.service loaded active running FOGPingHosts
      FOGScheduler.service loaded active running FOGScheduler
      FOGSnapinHash.service loaded active running FOGSnapinHash
      FOGSnapinReplicator.service loaded active running FOGSnapinReplicator

      seems all FOG related service is activated an running well.

      I am lost here. What’s and where is wrong?

      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by

        @cidy-long-0 said in Fog service is not accessible after reboot:

        The site could be temporarily unavailable or too busy. Try again in a few moments.

        This means the webserver is not running. Check with systemctl status httpd. Or maybe it’s a firewall that only was deactivated temporarily when installing FOG?

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        cidy.long 0C 1 Reply Last reply Reply Quote 0
        • cidy.long 0C
          cidy.long 0 @Sebastian Roth
          last edited by

          @Sebastian-Roth

          Thank you! I forgot about my firewall, once I shutdown my firewall, everything is fine.

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by

            @cidy-long-0 You can setup FOG with firewall but really need to know what you are doing. E.g. kernel updates through the web UI and image capture can be a problem if you get the firewall rules wrong.

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            1 Reply Last reply Reply Quote 0
            • [[undefined-on, S Sebastian Roth, ]]
            • 1 / 1
            • First post
              Last post

            147

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project