SAM takes several minutes to start

[Roberto Martinez_2]

In our almost-out-of-the-box rp3440, 4 cpu, 8Gb ram: I connect from my pc to the server console via ip to the MP, everything seems fine (I can log onto the system, do a ls for example,...), sam takes more than 1 minute to start (even to appear the initial screen), then another minute to show the list of SAM areas.


a "top" returns 3 cpus about 100% idle and another one at about 50%, there's a process called "stm" which has used about 10min. cpu.

Just sam seems to be slow, an "ls -lr" returns info very fast, so I'll discard the network between my pc and the server.

Any hints? What's "stm" for? why is it taking so much cpu?

thanks.

[Roberto Martinez_2]

btw, there's just the network connection to the remote console, the rest of NICs do not still have a network connection. May this have something to do about it?

[Robert-Jan Goossens_1]

Hi Roberto,

Check hostname resolution.

# grep -i hostname /etc/rc.config.d/netconf

# nslookup "hostname"
# nslookup "ip-hostname"

Regards,
Robert-Jan

[Roberto Martinez_2]

connecting the network cable to the first NIC solved the problem. THanks anyway, your answer hinted me the solution.