Tried to update to 2.1.1 and am getting the following error. At first the install failed with some access issues so i tried with sudo and am now getting this error. I’m not really sure what the “cannot run in wd” means.

@strawberry-3.141 Oh wow! Ran a pm2 stop mm and the ssh went back to exactly how it used to be. No lag at all and can use nano on the config file with zero lag (could even mouse wheel scroll perfectly).

Then starting MM back up (pm2 start mm) it seems to maintain the quick ssh speed. Upon a full reboot though it seems to get back to being slightly slower.

@strawberry-3.141 My cpu usage (using top) after the pi has booted up stays around 3-5% (using the top command raises this a bit). And memory usage doesnt seem out of control either.

top - 10:36:12 up 43 min,  3 users,  load average: 0.14, 0.12, 0.11
Tasks: 107 total,   1 running, 100 sleeping,   6 stopped,   0 zombie
%Cpu(s):  4.7 us,  1.0 sy,  0.0 ni, 93.9 id,  0.0 wa,  0.0 hi,  0.3 si,  0.0 st
KiB Mem:    445084 total,   340880 used,   104204 free,    26108 buffers
KiB Swap:   102396 total,        0 used,   102396 free.   159376 cached Mem

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND                                      
  611 pi        20   0  205560  77592  42308 S  3.3 17.4   1:35.69 midori                                       
 3581 pi        20   0    5232   2596   2160 R  1.6  0.6   0:00.38 top                                          
   60 root      20   0       0      0      0 S  0.3  0.0   0:02.04 kworker/0:2                                  
  594 root      19  -1  154840  47040  21040 S  0.3 10.6   0:16.78 Xorg                                         
 3241 pi        20   0   11940   3440   2768 S  0.3  0.8   0:00.89 sshd                                         
    1 root      20   0    5308   3776   2736 S  0.0  0.8   0:07.32 systemd                                      
    2 root      20   0       0      0      0 S  0.0  0.0   0:00.01 kthreadd                                     
    3 root      20   0       0      0      0 S  0.0  0.0   0:01.17 ksoftirqd/0  

Im using the following modules.

• profileswitcher, buttons, clock, calendar, compliments, current weather, weather forecast, wunderlist, newsfeed, calendar monthly, tube status, and system stats.

Thanks for the tips everyone.
@yawns I’m connected via wifi and in the same room as the router, nothing has changed here. I’ve attempted to add the UseDNS=no but it didnt seem to change the major lag im experiencing. i.e i type and it takes a few seconds for it to show up on the command line. But when I tried ‘UseDNS no’ (as this seemed to be the syntax in the file) it seemed to be a little speedier upon the next reboot! Not near as fast as it was a few weeks back but now i can get in and navigate around etc. Thanks!

I wonder if there is anything else that could be slowing it down, how does the UsDNS command speed things up like it did?

@Snille i’ve done an ls -alh in a few of the directories and have no large file name core. Would there be any other temp/log type of files that could be causing a slowdown?

@ianperrin thank you for that, i was also more just curious that i didn’t implement it incorrectly. This is a workaround i can live with.
Thank you.

@yawns thanks for the reply. Yes I’ve restarted it many-many times in the last few days. Valid question.

After coming back to my mirror after a month or so of not touching it as I’ve been quite happy with the set up I’ve noticed whenever im in SSH that its extremely slow. To the point of it becoming very difficult to even type on the command line let alone use nano.

I’m wondering if anyone has any ways I could troubleshoot why this is happening. I’ve not moved the physical Pi or changed anything. It used to run absolutely perfectly.

Any help would be greatly appreciated.

This module currently only says loading for drivers and constructors. Is this because the season hasnt started yet?

Is there a way to perhaps put a message/deactivate the module or something there if the season hasnt started?

@Hein-Jan Thanks for the workaround, i suppose rebooting nightly isnt ideal but if it fixes things I’ll give it a shot. I just don’t understand as it was working perfectly for so long, as I’m sure it is for others also. There must be something in either the wunderlist config or in the MM config that it doesnt like.

I’ve had two wunderlist lists running under each other for just under month now without issues, but now it seems like the lists are not updating at all?

I requested a new accesstoken and it worked again for a couple refreshes but ive come back and checked on it later in the day and the lists werent updating. I’ve restarted the MM and the lists dont seem to be loading at all.

It sort of seems like its rejecting the token, or the token is being locked out after some time. Has anyone else had this issue before?

edit: Also there are no errors at startup via pm2 logs.