OMV-Plugins not working on Fedaykin

  • And the dependencies:

    Code
    root@NAS:/# apt-cache unmet openmediavault-transmissionbt
    Package openmediavault-transmissionbt version 0.4~1.gbpfb7cc7 have unmet dependencies:
    Dependency: transmission-daemon (>= 2.42)
    Dependency: transmission-cli (>= 2.42)


    Code
    root@NAS:/# apt-cache unmet transmission-common
    root@NAS:/#


    Code
    root@NAS:/# apt-cache unmet transmission-cli
    root@NAS:/#


    Code
    root@NAS:/# apt-cache unmet transmission-daemon
    root@NAS:/#


    Guess that means no dependency errors with the three last ones.

  • New minidlna package 1.0.25-1 working. Default location for files.db is again /tmp/minidlna and logging working at /var/log


    before you upgrade pacakge in omv web gui people should do following:


    cd /etc
    cp minidlna.conf minidlna.conf-old


    then upgrade minidlna in omv web gui and then:


    service minidlna stop
    rm /tmp/minidlna/files.db
    rm /var/cache/minidlna/files.db
    cd /etc
    cp minidlna.conf-old minidlna.conf
    service minidlna start


    That should do it.......

  • Quote from "Marcel.Beck"

    Please run an apt-get update and try to install openmediavault-transmissionbt again.


    I have also pushed a new minidlna Package, maybe someone can test this, too.


    I ran a check from webui and a lot of lib* and transmission updates were avaliable. I installed all but the minidlna. (I dare not test it before the transmission issue has been solved, since I finally got minidlna 1.0.24 to work properly this evening with help from tekbebe) :)


    After this, the openmediavault-transmissionbt was avaliable again in the plugins-menu and I installed it from there.
    But when activating the server, this error appears:

    Code
    Fejl #3003:
    exception 'OMVException' with message 'Failed to get configuration (xpath=//services/transmissionbt)' in /var/www/openmediavault/module/transmissionbt.inc:51
    Stack trace:
    #0 /var/www/openmediavault/rpc/services.inc(41): TransmissionBTModule->getStatus()
    #1 [internal function]: ServicesRpc->getStatus(Array)
    #2 /usr/share/php/openmediavault/rpc.inc(265): call_user_func_array(Array, Array)
    #3 /usr/share/php/openmediavault/rpc.inc(98): OMVRpc::exec('Services', 'getStatus', Array)
    #4 /var/www/openmediavault/rpc.php(44): OMVJsonRpcServer->handle()
    #5 {main}


    I can the dependency checks again, and this came up:

    Code
    root@NAS:~# apt-cache unmet transmission-cli
    PAckage transmission-cli version 2.42-0ubuntu0.11.04.2 has unmet dependencies:
    Suggested: transmission-gtk (= 2.42-0ubuntu0.11.04.2)


    The other ones previously tested are fine.

  • UPDATE::
    @tekkbebe:
    Just installed the new minidlna 1.0.25-1 and it's purring like a kitten! :)
    Your instructions were really helpful and hasslefree. Thanks man!
    Marcel:
    The transmission is still not working. See the above post.

  • Quote from "deviouz"

    ~snap~
    I can the dependency checks again, and this came up:

    Code
    root@NAS:~# apt-cache unmet transmission-cli
    PAckage transmission-cli version 2.42-0ubuntu0.11.04.2 has unmet dependencies:
    Suggested: transmission-gtk (= 2.42-0ubuntu0.11.04.2)


    The other ones previously tested are fine.


    Okay, this is hard to figure out...
    Maybe one of the dependencies transmission-cli has, has an unmet dependency.


    Unfortunately i do not know how to figure this out, with just one command.


    You can try this:


    You need to check apt-cache unmet <package name> for each package listened as depends.
    Maybe there is something wrong.


    Did you ever activate the glass repository?

  • Marcel
    First of all; Thank you for taking this time to help. I truly appreciate it.


    I never activated the glass or donald repository. As described earlier it's an entirely new installation of OMV upgraded to fedaykin and witj the OMV-pluging 0.4 installed.


    This is what I get from a apt-get cache depends transmission-cli:


    I can see from youre client name that you possibly run a 64bit version, and I don't know if it have any significance, but I have a i386 version.


    I ran the unmet check on every package in the list above and none of them reported any errors. Only transmission-cli with the same dependency error as before.


    Again, thanks a lot for your help. :)

  • I cannot even reproduce this with a i386 version.


    I am getting the same message:

    Code
    root@omv32bittest:/etc/apt/sources.list.d# apt-cache unmet transmission-cli
    Package transmission-cli version 2.42-0ubuntu0.11.04.2 has an unmet dep:
    Suggests: transmission-gtk (= 2.42-0ubuntu0.11.04.2)


    This is just because transmission-gtk has unmet dependencies, but this is just a suggests package.


    But the Transmission Daemon is running fine.


    Can you post the output of:

    Code
    apt-cache policy transmission-cli
    apt-cache policy transmission-daemon
    apt-cache policy transmission-common
    apt-cache policy openmediavault-transmissionbt


    Again?

  • Sure. Here it is.


    I tried removal and purging and hereafter installation of:
    - transmission-cli
    - tranmission-common
    - transmission-daemon
    - openmediavault-transmissionbt
    and see what happened when installing the daemon:

    Code
    Starting bittorrent daemon: transmission-daemonIllegal instruction
    invoke-rc.d: initscript transmission-daemon, action "start" failed.
    dpkg: error when processing transmission-daemon (--configure):
    subprocess installed post-installation-script returned error exit status 132
    configured to not write apport reports
    Errors were encountered while processing:
    transmission-daemon
    E: Sub-process /usr/bin/dpkg returned an error code (1)


    Is it a clue?

  • Quote from "drap"

    Hi, just wondering if greyhole will be ported soon? If not, is there anyway of using it in the mean time whilst waiting for the plugin?
    Thanks,


    Marcel said it would take a couple of weeks but that might have been a week ago.

    omv 5.6.0 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.5.3
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Just wanted to bump this thread. It's still an issue. :/


  • Quote from "Marcel.Beck"

    This is an issue of your setup.
    And this is not an issue with any of the packages.


    You need to check your logfiles.


    Please read the error message, the transmission daemon can not be started, now one here can see why. This is something you must figure out.


    It has been an issue with the three last setups. Ive tried reinstalling the entire system several times now, trying to sort out if the problem may be caused by the order which I install the packages in.
    This dosn't seems to be that case. It always ends with this error. I even tried it on another hardware system, just to see if it were hardware related - but it wasn't.
    The log files dosn't say more than posted previously in this thread.
    You earlier asked me to run a few tests and commands, and now you tell me Im on my own?
    I just have to find another way of using bittorrent, I guess.. :|

  • Quote from "deviouz"

    It has been an issue with the three last setups. Ive tried reinstalling the entire system several times now, trying to sort out if the problem may be caused by the order which I install the packages in.
    This dosn't seems to be that case. It always ends with this error. I even tried it on another hardware system, just to see if it were hardware related - but it wasn't.
    The log files dosn't say more than posted previously in this thread.
    You earlier asked me to run a few tests and commands, and now you tell me Im on my own?
    I just have to find another way of using bittorrent, I guess.. :|



    You had to edit /etc/default/transmission-daemon and replace all occurrenses of

    Code
    &quot;

    with

    Code
    "
  • I was also having problems with the plugins, not able to connect to plugins server.I fixed the problem by adding the information for the DNS server to point to my router ip address.


    Now everything is working fine.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!