Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
emulab-devel
emulab-devel
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 143
    • Issues 143
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 6
    • Merge Requests 6
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • emulab
  • emulab-develemulab-devel
  • Issues
  • #504

Closed
Open
Opened May 24, 2019 by Mike Hibler@hiblerMaintainer

`slothd` run too soon?

I happen to notice when I was setting up some vlan devices on a client, that slothd complains:

...
Starting slothd usage detector
slothd: Failed to get experiment net iface name for MAC
slothd: Failed to get experiment net iface name for MAC
slothd: Failed to get experiment net iface name for MAC
...

because the interfaces in question are vlan devices that have not been created yet (on FreeBSD) because rc.config (which runs rc.ifconfig) has not been run yet.

At this point I am not sure if slothd will pick these up later or whether we just don't report stats for the vlan interfaces or whether this is just a problem on FreeBSD.

We run slothd as early as we do so that it gets run on nodes that are free. I think this dates back to the days when free nodes sat in an OS instead of in pxeboot.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: emulab/emulab-devel#504