Categories

  • 12k Topics
    114k Posts
    H

    Hello,

    I’ve ran into a problem. When upgrading from Debian 12 to Debian 13 I no longer can get to the webpage for fog. I get a 503 service unavailable. After seeing that I decided to re-run the installer to see if that would help but then I get the following dependency conflicts and was wondering if anyone has ran into this yet with Debian 13 Trixie.

    The following information may help to resolve the situation:

    The following packages have unmet dependencies:
    systemd-sysv : Conflicts: initscripts but 3.14-4 is to be installed
    Conflicts: insserv but 1.26.0-1 is to be installed
    Conflicts: startpar but 0.66-1 is to be installed
    Conflicts: sysv-rc but 3.14-4 is to be installed
    Conflicts: sysvinit-core but 3.14-4 is to be installed
    sysvinit-core : Conflicts: systemd-sysv but 257.9-1~deb13u1 is to be installed
    Recommends: orphan-sysvinit-scripts but it is not going to be installed
    E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
    E: The following information from --solver 3.0 may provide additional context:
    Unable to satisfy dependencies. Reached two conflicting decisions:

    sysvinit-core:amd64 is not selected for install because: systemd-sysv:amd64 is selected for install systemd-sysv:amd64 is available in versions 257.9-1~deb13u1, 257.8-1~deb13u2
    [selected systemd-sysv:amd64=257.9-1~deb13u1 for install] sysvinit-core:amd64 Conflicts systemd-sysv
    [selected systemd-sysv:amd64=257.9-1~deb13u1]
    For context, additional choices that could not be installed: In systemd-sysv:amd64 is available in versions 257.9-1~deb13u1, 257.8-1~deb13u2: systemd-sysv:amd64=257.8-1~deb13u2 is not selected for install sysvinit-core:amd64 is selected for install because: sysv-rc-conf:amd64=0.99-10 is selected for install sysv-rc-conf:amd64 Depends sysvinit-core
  • Get the latest news on what's happening.
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    2k Topics
    19k Posts
    Cire3C

    @youzersef Ok, see how long it takes me to get back on a project…lol

    I did some more looking, and found yes, the GUI will re-write the dhcp config file. However I did some more reading and I guess services.inc determines what is written by the GUI.

    Sorry, not a CLI guy, and I love the quick and easy edits, viewing issues that the GUI provides. Like Fog ! However my servers are headless…lol

    Anyway, looking that route now, and will update if I find how Negate wants services edited so when it reboots, DHCP will remain.

    Determined 🙂

    Any thank you everyone here . This place has always been great for information !

  • Report bugs, request features, or get the latest progress.
    2k Topics
    21k Posts
    M

    Re: rocky linux 9.6 quirks & php 8

    new topic - porting images and metadata from 1.5.9 to 1.5.10

    @Tom-Elliott

    So I finally started needing to use this install as our old server is failing. Anyway, what I am running into a problem now deleting and using images which I transferred over from our 1.5.9 fog set up. I get errors on imaging these undefined property. I earlier had errors in the list all images directory - which updated each image manually - attemping to check in fails. - the exact line is in /var/www/html/fog/lib/fog/task.class.php

    I think there is something still missing in the images I ported over from out 1.5.9 set up. my colleague who uses this server loaded the metadata from the 1.5.9 set up and is where these errors started, When I try to delete a host or image - I get a ‘invalid’ login error. I have the firewall and SElinux disabled on this server as it is not on the internet.

    I am using bzimage version 6.12.35 I can add a host and PXE boot so that is not the issue. here. I tried to scrap all these images and just manually add all these reusing the image files I have but I can’t delete anything,

    Sure I can go full nuclear and reinstall everything from scratch but kinda want to avoid that.

    I spent some time with mysql trying to get around the 'invaild login" error issue I am running into.

    I can try to run the installer again so see if I can wipe this database and schema.

    Matt

139

Online

12.5k

Users

17.5k

Topics

156.3k

Posts