FedoraForum.org - Fedora Support Forums and Community
Page 1 of 2 12 LastLast
Results 1 to 15 of 17
  1. #1
    Join Date
    Jun 2012
    Location
    Nyír1
    Posts
    5
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Failed to start LSB: Init script for TCSD.

    Hi all,

    i just checked my boot.log, and i found an error:

    "Failed to start LSB: Init script for TCSD.
    See 'systemctl status tcsd.service' for details."

    My tcsd service status report:

    tcsd.service - LSB: Init script for TCSD
    Loaded: loaded (/etc/rc.d/init.d/tcsd)
    Active: failed (Result: exit-code) since Fri, 29 Jun 2012 16:44:11 +0200; 3min 12s ago
    Process: 575 ExecStart=/etc/rc.d/init.d/tcsd start (code=exited, status=137)
    CGroup: name=systemd:/system/tcsd.service

    What does it mean?
    I dont experience any problem with the Fedora, so its just simple curiosity.

    Thanks for your answears.

  2. #2
    Camberwell Guest

    Re: Failed to start LSB: Init script for TCSD.

    I noticed this appeared on mine aswell after a recent update

    apparently yum provides /usr/sbin/tcsd tells me that its a package called trousers

    and yum info trousers tells me..


    Name : trousers
    Arch : x86_64
    Version : 0.3.6
    Release : 2.fc17
    Size : 787 k
    Repo : installed
    From repo : fedora
    Summary : TCG's Software Stack v1.2
    URL : http://trousers.sourceforge.net
    Licence : CPL
    Description : TrouSerS is an implementation of the Trusted Computing Group's Software Stack
    : (TSS) specification. You can use TrouSerS to write applications that make use
    : of your TPM hardware. TPM hardware can create, store and use RSA keys
    : securely (without ever being exposed in memory), verify a platform's software
    : state using cryptographic hashes and more.

    so I'm still none the wiser really, lol

    Martin

  3. #3
    Join Date
    Jun 2012
    Location
    Nyír1
    Posts
    5
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start LSB: Init script for TCSD.

    Thanks for your reply;
    well i tried to reinstall this trousers package you mentioned, but it makes no difference, still get the error message.
    Meanwhile i checked the website, but the latest news from '08, so i guess we wont get a fast fix for this..

  4. #4
    Camberwell Guest

    Re: Failed to start LSB: Init script for TCSD.

    i suspect you could just do, systemctl disable tcsd.service, to get rid of the message, however i'm not sure sure if this service is needed or not.

    but as it fails to start anyway and my system seems unaffected, i suspect not.

    Martin

  5. #5
    Join Date
    Jun 2012
    Location
    Nyír1
    Posts
    5
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start LSB: Init script for TCSD.

    because im not experiencing any problems in the system, i guess im just gonna leave it then. But the problem still persists, so this thread remains unsolved.

  6. #6
    Join Date
    Jan 2011
    Location
    NYC,NY
    Posts
    1,314
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start LSB: Init script for TCSD.

    Trousers is a dependency package, which got installed in last night's updates.

    It started tscd which is not available.

    Edit:
    As others have already mentioned, you can either disable it(systemctl disable tcsd.service), or ignore it becoz it means no harm to your system. But sure its a bug.
    HP 14 DQ 1025CL | Intel Core i5-1035G1 -Icelake 256GB SSD

  7. #7
    Join Date
    May 2005
    Posts
    29
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start LSB: Init script for TCSD.

    I had the same problem. On my systems trousers (TCSD) is a dependency for openvpn , which I have no use for at this time. In the case of a software release that is buggy and non-essential, deleting it and moving on is the best course. I found that "yum erase trousers" solved the problem.

  8. #8
    Join Date
    Apr 2012
    Location
    Mexico
    Posts
    7
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start LSB: Init script for TCSD.

    I get the same error

    tcsd.service - LSB: Init script for TCSD
    Loaded: loaded (/etc/rc.d/init.d/tcsd)
    Active: failed since Sun, 16 Sep 2012 19:30:01 -0500; 16min ago
    CGroup: name=systemd:/system/tcsd.service

    Warning: Unit file changed on disk, 'systemctl --system daemon-reload' recommended.

  9. #9
    Join Date
    Aug 2009
    Posts
    11,390
    Mentioned
    98 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start LSB: Init script for TCSD.

    All you have to do to fix that error:

    Code:
    su-
    (root password)
    
    systemctl disable tcsd.service
    The only time tcsd.service is wanted and the only way tcsd will run is if you have a machine that has a TPM chip on it. It was mainly just put on laptops until just recently (within the last year or so)

  10. #10
    Join Date
    Jul 2012
    Location
    China
    Posts
    10
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start LSB: Init script for TCSD.

    I have encontered the same problem.
    But
    what is it used for, tcsd.service?

  11. #11
    Join Date
    Jun 2004
    Location
    Maryland, US
    Posts
    15,399
    Mentioned
    186 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start LSB: Init script for TCSD.

    Quote Originally Posted by runmachine
    I have encontered the same problem.
    But
    what is it used for, tcsd.service?
    It stands for "TrouSerS TCG Core Services daemon", it's a daemon for support of Trusted Computing

    https://en.wikipedia.org/wiki/Trusted_Computing_Group
    http://trousers.sourceforge.net/
    http://sourceforge.net/projects/tpmdd/


    It's related to TPM which is Trusted Platform Module, which tries to ensure your computer will only run trusted and confirmed softwares. One thing it might do is offer a way for a software to only run on a licensed copy of an OS and not a hacked one (for example a Hackintosh vs real Mac OS X). To even work, your computer has to have a TPM capable chipset (many don't). If you're not using it, just disable the tcsd service (see post #9)

  12. #12
    Join Date
    Jul 2012
    Location
    China
    Posts
    10
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start LSB: Init script for TCSD.

    Quote Originally Posted by marko
    It stands for "TrouSerS TCG Core Services daemon", it's a daemon for support of Trusted Computing

    https://en.wikipedia.org/wiki/Trusted_Computing_Group
    http://trousers.sourceforge.net/
    http://sourceforge.net/projects/tpmdd/


    It's related to TPM which is Trusted Platform Module, which tries to ensure your computer will only run trusted and confirmed softwares. One thing it might do is offer a way for a software to only run on a licensed copy of an OS and not a hacked one (for example a Hackintosh vs real Mac OS X). To even work, your computer has to have a TPM capable chipset (many don't). If you're not using it, just disable the tcsd service (see post #9)
    Thank you for reply
    Last edited by runmachine; 25th September 2012 at 03:58 PM.

  13. #13
    Join Date
    Nov 2012
    Location
    Uruguay
    Posts
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start LSB: Init script for TCSD.

    Hi folks.

    I´m getting the same error during boot, except that the system won´t boot. It stops where it starts the display manager, and the only errors I see are the one the OP is getting and "Failed to start LSB: Starts and stops logging and scanning of iSCSI devices".

    I try disabling TCSD as explained above, on emergency mode (the only mode I can access or at least know how to) and it says I don´t have the priviledges to do it, even though I´m root.

    I recently switched from windows, so please be patient and explain things to me the way you would to a five year old

    Thanks!

  14. #14
    Join Date
    May 2010
    Posts
    220
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start LSB: Init script for TCSD.

    I've gotten tired of looking at this error, so I've finally decided to do something about it. I've turned the offending/unnecessary service off. Although the previously recommended commands do work, the screen feedback suggests that you should be using chkconfigl to disable the service:

    Code:
    # systemctl disable tcsd.service
    tcsd.service is not a native service, redirecting to /sbin/chkconfig.
    Executing /sbin/chkconfig tcsd off
    #
    It is a mystery to me why services like this, which are dependent upon the existence of a non-standard/specialized chip in order to function, are being activated by default on a desktop installation. The only answer that I can think of is that Linux is suffering from more and more Windows-type code-bloat. It would seem that some developer isn't paying attention to what's needed in the default F17 install and what isn't. This should probably be reported as a bug.

  15. #15
    Join Date
    Sep 2010
    Location
    Quebec, Canada
    Posts
    26
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start LSB: Init script for TCSD.

    I don't like to post when I don't have the answers but a few things are in order here...

    First thing first:

    Fermin, Welcome to Linux, it is not the same as Windows... as in you can do much more but you have to study and read up on things to finally know what you are doing. But then again, Linux is now so big that most of the time you'll only partially know what you're doing. The main difference between Windows and Linux is that most of the time, when you need to reinstall Windows, it's not your fault... it crashes by itself. When you need to reinstall Linux it's because you yourself hosed your own system... don't worry, it only takes one slash too many: Never do " chown usernameX: ../ " when you don't know where you are (if you don't understand that last one it's not important... just remember that it happens to all of us).

    As for this whole thread, things are kind of in a flux right now... in between System V and Systemd and getting lost from iptables to firewald...just remember what Michal Jaegermann said when answering a RedHat bug report: " there is no good mechanism how to use similar ways with systemd. Apparently you can put that on a banner and carry it around. "
    MotherDawg
    I own crappy boxes
    I do RPMs -- CentOs & Fedora
    I loose countless hours tweaking games that I barely play... just to see if the mod worked...

Page 1 of 2 12 LastLast

Similar Threads

  1. Replies: 1
    Last Post: 13th February 2014, 03:28 PM
  2. Replies: 4
    Last Post: 14th July 2013, 02:25 PM
  3. FC8, Init.d script start order resetting automatically
    By jpeterse in forum Using Fedora
    Replies: 1
    Last Post: 30th March 2009, 06:43 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •