SHARE
TWEET

Untitled

a guest Jun 12th, 2018 60 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. x23piracy
  2.  
  3. I have a strange wol problem, tom please help me
  4. x23piracy
  5.  
  6. Hi Tom, is there any place i can check to see if fog is waking up my computers again and again? i really have no idea what is causing this but after removing the host from fog they still turn on. I am busted :(
  7. x23piracy
  8.  
  9. Hi Tom the Wake up Problem is 100% FOG caused, if i turn the fog server off machine does not wake up, when i boot fog and shutdown the computer that always turns on it happens again. The computer is no more fog registered but fog is causing the power on thats for sure.
  10.  
  11. Could you please help me in a way?
  12.  
  13. https://forums.fogproject.org/post/75832 i am crying
  14.  
  15. can i check something in fog db where maybe a wol job is pending again and again?
  16. x23piracy
  17.  
  18. I could also remove the fog service from the problematic computer, when fog server is running it will wake that computer also if host is not registered to fog, i really need you to find out why fog is sending wol to that computers
  19.  
  20. can we please check my database to see whats causing this bad issue?
  21. x23piracy
  22.  
  23. FYI: https://i.imgur.com/RxMHp1V.png
  24.  
  25. can i reset my database without loosing all my settings? i just want to delete anything host related
  26. x23piracy
  27.  
  28. FYI again, sorry for bugging such hard but thats a big problem to me: https://i.imgur.com/gZFw8r7.png
  29. x23piracy
  30.  
  31. one last: https://i.imgur.com/DywyWTl.png
  32. x23piracy
  33.  
  34. Joe asked me if we two can maybe look for my issue, please give me a message if you have time tom, this is really a big problem to me 16 workstations turn on again and again and our employess hunting for my head i need help please.
  35. Tom Elliott
  36.  
  37. I’m so confused man.
  38.  
  39. only systems that are NOT registered are running WOL?
  40.  
  41. while registered systems are fine?
  42. x23piracy
  43.  
  44. hi tom ok lets start from scratch
  45.  
  46. i have 16 new computer, i had all of them registered to fog and deploayed my win 10 image with fog client integrated
  47. Tom Elliott
  48.  
  49. yep.
  50. x23piracy
  51.  
  52. while setup them up i could mention that they turn on by magic always when i shutted them dowm
  53. Tom Elliott
  54.  
  55. okay
  56. x23piracy
  57.  
  58. then i removed all that clients from fog and also removed the fog service from one of the machines
  59.  
  60. but they still turn on by magic
  61. Tom Elliott
  62.  
  63. okay
  64. x23piracy
  65.  
  66. when they boot the do a network boot not just a simple switch on
  67. Tom Elliott
  68.  
  69. that doesn’t mean much
  70. x23piracy
  71.  
  72. i can see this because they boot into fog menu and them the 5 second timeout let them boot os
  73. Tom Elliott
  74.  
  75. if the systems are setup to pxe boot first
  76.  
  77. that would happen anyway
  78.  
  79. but
  80. x23piracy
  81.  
  82. when i shutdown the fog server these clients dont wake up
  83. Tom Elliott
  84.  
  85. i need a log
  86.  
  87. of the /opt/fog/fogscheduler.log
  88. x23piracy
  89.  
  90. is there somethin for direct pastebin upload or something ?
  91.  
  92. could i reach the log via webif else i need winscp
  93. Tom Elliott
  94.  
  95. you can get it from the log viewer utility built into the gui
  96. x23piracy
  97.  
  98. i grabbed it from winscp
  99.  
  100. http://pastebin.com/BMNmi44J
  101.  
  102. wayne recommended to temporarily shutdown fogscheduler
  103.  
  104. why do i have entry in tasks table? shouldn’t it be empty if i dont have any scheduled or running tasks?
  105. Tom Elliott
  106.  
  107. tasks are handled by states
  108.  
  109. 1,2,3 are “queued, inline, in progress”
  110.  
  111. 4,5 are complete and cancelled
  112. x23piracy
  113.  
  114. they all have 4 or 5
  115. Tom Elliott
  116.  
  117. yep
  118.  
  119. that’s fine
  120. x23piracy
  121.  
  122. i’ve stop fogscheduler
  123. Tom Elliott
  124.  
  125. have hosts stopped WOL?
  126. x23piracy
  127.  
  128. i will now shutdown the workstation to see if it turns on again
  129.  
  130. i just stopped it some seconds ago wait…
  131.  
  132. is it a problem that i’Ve cleared tasks table?
  133.  
  134. it’s empty now, didn’t knew that is not important if there are entrys
  135.  
  136. the workstation has switched on again while fogscheduler was stopped
  137. Tom Elliott
  138.  
  139. okay
  140.  
  141. so what’s output of
  142.  
  143. crontab -l
  144. x23piracy
  145. m h dom mon dow command
  146.  
  147. @reboot sudo bash -c ‘/home/fog/restart_services.sh’ &
  148. root@fog:/opt/fog/log#
  149.  
  150. ups sorry for the big letters :D
  151.  
  152. the only cronline is: @reboot sudo bash -c ‘/home/fog/restart_services.sh’ &
  153. Tom Elliott
  154.  
  155. well it’s not something FOG has done that’s waking these systems up.
  156.  
  157. it can’t be
  158.  
  159. fogscheduler is the ONLY service that performs wake on lan operations
  160.  
  161. you can stop all fog services as a test.
  162. x23piracy
  163.  
  164. it is i would be money, when i now shutdown fog server and after that the workstation it does not turn on anymore
  165. Tom Elliott
  166.  
  167. systemctl stop FOGScheduler
  168. x23piracy
  169.  
  170. tom i swear to you this is something fog is doing
  171. Tom Elliott
  172.  
  173. systemctl stop FOGPingHosts
  174.  
  175. no
  176.  
  177. it’s not
  178.  
  179. i’m not saying your fog server isn’t doing anything
  180. x23piracy
  181.  
  182. what else could it be then?
  183. Tom Elliott
  184.  
  185. but it’s not anything FOG is doing
  186. x23piracy
  187.  
  188. cosmic radiation ? :D
  189. Tom Elliott
  190.  
  191. FOGScheduler is the only thing that cycles to turn systems on.
  192.  
  193. and even then, it can only do so with systems that are registered.
  194.  
  195. do you have other nodes?
  196. x23piracy
  197.  
  198. now i have stopped both services fogscheduler and pinghosts
  199. Tom Elliott
  200.  
  201. pinghosts has nothing to do with it
  202.  
  203. do you have multiple nodes
  204. x23piracy
  205.  
  206. yes i have one storage node
  207. Tom Elliott
  208.  
  209. And the main server?
  210.  
  211. so you have 2 “nodes”?
  212. x23piracy
  213.  
  214. what about the main server?
  215.  
  216. yes 2 nodes
  217. Tom Elliott
  218.  
  219. okay
  220.  
  221. and the other node
  222.  
  223. can you access it via GUI?
  224.  
  225. so
  226.  
  227. browser
  228.  
  229. http://<othernodesIP>/fog/
  230. x23piracy
  231.  
  232. first normal fog with webif and less storage (vm) second physical machine with 4tb as storage node
  233.  
  234. This is a storage node, please do not access the web ui here!
  235. Tom Elliott
  236.  
  237. okay
  238.  
  239. now on that node
  240.  
  241. what about it’s FOGService?
  242. x23piracy
  243.  
  244. i haven’t touched the storage node while main fog server is offlien
  245.  
  246. i was not thinking about the maybe the storage node is doing the problem
  247. Tom Elliott
  248.  
  249. can you please do it?
  250.  
  251. i need to find why it’s doing this
  252. x23piracy
  253.  
  254. ok what should i do with the storage node?
  255.  
  256. also disable fogscheduler?
  257. Tom Elliott
  258.  
  259. just get the log first
  260. x23piracy
  261.  
  262. ok wait a second
  263.  
  264. the only entry in fogscheduler.log on the storage node is: [08-05-16 5:53:05 pm] * No tasks found!
  265. Tom Elliott
  266.  
  267. and output of
  268.  
  269. systemctl -l status FOGScheduler
  270. x23piracy
  271.  
  272. ubuntu!
  273.  
  274. service?
  275. Tom Elliott
  276.  
  277. Doesn’t mean anything
  278.  
  279. Ubuntu 15 and up uses systemctl
  280. x23piracy
  281.  
  282. i get comand not found
  283. Tom Elliott
  284.  
  285. so
  286.  
  287. go ahead and stop the FOGScheduler
  288. x23piracy
  289.  
  290. ok it’s stopped
  291. Tom Elliott
  292.  
  293. now you stopped PingHosts on the server too?
  294. x23piracy
  295.  
  296. no just scheduler
  297. Tom Elliott
  298.  
  299. go ahead and restart fogscheduler
  300.  
  301. and stop pinghosts
  302. x23piracy
  303.  
  304. ok started scheduler again and pinghosts wasn’t running because: * Stopping FOG Computer Imaging Solution: FOGPingHosts start-stop-daemon: warning: failed to kill 1570: No such process
  305.  
  306. why do you think the storage node is maybe causing this, while fog main server is off and only storage node is running workstations remain off
  307.  
  308. the problem only exists when main fog is active
  309. Tom Elliott
  310.  
  311. just trying to see all angles
  312. x23piracy
  313.  
  314. ok understand
  315.  
  316. you can also have system access again if you like
  317.  
  318. maybe we can see live whats triggering the wol
  319. x23piracy
  320.  
  321. i have turned off the workstation again and since 2-3 minutes it remains off
  322. Tom Elliott
  323.  
  324. so turn back on ping hosts.
  325. x23piracy
  326.  
  327. on both machines?
  328. Tom Elliott
  329.  
  330. and what’s in the /opt/fog/log/pinghosts.log file
  331.  
  332. only the main server
  333. x23piracy
  334.  
  335. pinghosts start for both?
  336. Tom Elliott
  337.  
  338. just the main server
  339. x23piracy
  340.  
  341. lol
  342.  
  343. immediatelly the workstation turned on
  344.  
  345. i could here the relay from the kvm switch
  346.  
  347. service FOGPingHosts start and 1-2 seconds later workstation turned on
  348. Tom Elliott
  349.  
  350. adn what does the pinghosts.log file show
  351. x23piracy
  352.  
  353. http://pastebin.com/bGBnVhCz
  354.  
  355. should i try again? stop pinghosts, shutdown workstation, start pinghosts and see if it turns on immediatelly?
  356.  
  357. ok did it and it’s the same 2 seconds after starting the pinghosts service the workstation switched on
  358.  
  359. i can do it a third time if you like
  360. x23piracy
  361.  
  362. it seems that fogpinghosts i causing this
  363.  
  364. disable that service, shutdown the problematic workstation, enable the pinghosts service again and exactly 2 seconds later the workstation turns on
  365.  
  366. i did that 2 times, and i will also happen if i try it a third time
  367. Tom Elliott
  368.  
  369. okay
  370.  
  371. i’m looking at ping hosts
  372.  
  373. but what’s most intriguing
  374.  
  375. there’s no code to send any packets to unknown hosts
  376.  
  377. can you do a Teamviewer session?
  378. x23piracy
  379.  
  380. sure
  381.  
  382. 285 312 065
  383.  
  384. 8120
  385.  
  386. i will open you a cmd with permanent ping to the workstation that turns on auto
  387. Tom Elliott
  388.  
  389. no need
  390. x23piracy
  391.  
  392. so i need to powercfg -h now and you can workaround that also by fog?
  393. Tom Elliott
  394.  
  395. I cannot workaround by fog.
  396.  
  397. There is simply no way for me to.
  398.  
  399. You can workaround it by disabling the ping service
  400.  
  401. this can be done on the GUI
  402.  
  403. FOG Configuration Page->FOG Settings->General Settings->FOG_HOST_LOOKUP
  404. x23piracy
  405.  
  406. powercfg- -h off right?
  407. Tom Elliott
  408.  
  409. uncheck the box
  410.  
  411. yes
  412.  
  413. powercfg -h off
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!
 
Top