How can I keep a player from “shutting down” after a streak of bad rolls?

In my sessions I’ve repeatedly noted that after a few bad rolls, one of my players (age 20) seems to become reclusive and stop paying attention.

Now I’ve tried various methods to get the player to pay attention again, but it seems that no matter how much his PC is punished or rewarded in game, even to the point of almost dieing to a hefty bag of gold, that this player did not care. I’ve even tried abstract methods, and given him a verbal slap, getting the other players to laugh at his PCs expense just to see if he’d dignify his character. Complete disconnect. The Player didn’t even care.

A Few rounds later, the dice rolls are in his favor, and suddenly, he cares about the story again! Participation happens, and the players are moving nicely.

This is bad for both of us. For me because suddenly I’ve got a brain dead PC that is being lugged around, slowing the game. For him, because he isn’t enjoying the game.

How do I as a DM prevent the disconnect that happens when players are on a bad luck streak?

Apache2 shutting down after a while

I build my own server on EC2 this weekend, everything goes well and my server is running, at least for a while, until shutdown.

First of all, I’m starting the server with sudo service apache2 status and everything is perfect, my server starts and I am able to navigate around my webpage.

Then, suddenly the server stops running (the EC2 instance works perfect) when I do sudo service apache2 status

I get this output:

apache2.service - The Apache HTTP Server    Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)   Drop-In: /lib/systemd/system/apache2.service.d            └─apache2-systemd.conf    Active: failed (Result: exit-code) since Tue 2019-07-16 01:28:00 UTC; 54min ago   Process: 18543 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)  Main PID: 18565 (code=exited, status=1/FAILURE)  Jul 15 21:17:38 ip-172-31-9-236 systemd[1]: Starting The Apache HTTP Server... Jul 15 21:17:38 ip-172-31-9-236 systemd[1]: Started The Apache HTTP Server. Jul 16 01:28:00 ip-172-31-9-236 systemd[1]: apache2.service: Main process exited, code=exited, status=1/FAILURE Jul 16 01:28:00 ip-172-31-9-236 systemd[1]: apache2.service: Failed with result 'exit-code'. 

And I really don’t know why.

I’m using EC2 from amazon with a route53 and https from cerbot. The /var/log/apache2/error.log output is nothing.

Laptop keeps shutting down while updating or download from store

I am in need of some help, first of all i like to tell you guys that i am quite new in Linux so in advance, sorry if i asked or said some stupid thing in my further post. So lets begin, My laptop is Dell Latitude E5520. ( i7 2nd Gen, 500 GB Hard Disk, 8 GB Ram) -[Dual Boot = Windows 10 / Ubuntu] I have been using this laptop with Windows 10 for quite some time now with no issue whatsoever, just recently for development purpose i Dual boot my system with Ubuntu. but now i am facing random shutdown issue in ubuntu. (Its still running fine on Windows 10) Shutdown are occurring when i try to update or download something new from store (Something to keep in mind is that if i use terminal to update or download, then there is no issue). I tried to search for random shutdown problem on ubuntu and find many solution and discussion but all of those were somehow related to hardware problem like hardware failure or overheating…. which is not the issue for me as i am still using Windows 10 with no issue on the same laptop and even ubuntu as long as i dont download or update something (Just recently i downloaded spotify from store and the laptop suddenly gave me popup for shutdown, and even when i click cancel on the dialog it still shuts down in next 3-5 secs. So if anyone have any suggestion for me please do tell me… i dont know what to do anymore.

Thank You

Why would a background process remain active after shutting down?

So I was playing around with Bash in a Terminal:

while true; do echo $  (date "+%r") >/tmp/test && sleep 10; done & 

This was a bad idea. The & appended at the very end made the loop run infinitely…

I was finally able to fully kill the parent process. But I noticed the while loop persisted even after rebooting. The “Reopen windows after logging back in” feature is disabled. Why might the above command remain active even after fully shutting down?

MBP shutting down during sleep

I usually put my 2018 MBP into sleep by closing the lid (without any program open) and next time I only need to open the lid and unlock with fingerprint. However, it recently got an annoying behavior by occasionally shutting down during sleep, forcing me to login with password later.

Here is an excerpt from pmset -g log command:

Time stamp                Domain                Message                                                                     Duration    Delay      ==========                ======                =======                                                                     ========    =====      UUID: 34379762-xxxx-xxxx-xxxx-xxxxxxxxxxxx 2019-06-11 03:19:05 +0700 Notification          Display is turned off                                                                  2019-06-11 03:19:05 +0700 Assertions            PID 96(hidd) Summary UserIsActive "com.apple.iohideventsystem.queue.tickle.4294969463.3" 00:00:03  id:0x0x900008230 [System: DeclUser kDisp]           2019-06-11 03:19:05 +0700 Assertions            PID 74(apsd) Summary ApplePushServiceTask "com.apple.apsd-recreatecourierstate-push.apple.com" 00:00:02  id:0x0xb00008235 [System: DeclUser kDisp]           2019-06-11 03:19:05 +0700 Assertions            PID 74(apsd) Summary ApplePushServiceTask "com.apple.apsd-recreatecourierstate-sandbox.push.apple.com" 00:00:02  id:0x0xb00008234 [System: DeclUser kDisp]           2019-06-11 03:19:05 +0700 Assertions            Kernel Idle sleep preventers: -None-           2019-06-11 03:19:05 +0700 Assertions            PID 54(powerd) Created InternalPreventSleep "com.apple.powermanagement.darkwakelinger" 00:00:00  id:0x0xd00008239 [System: PrevIdle DeclUser SRPrevSleep kCPU kDisp]           2019-06-11 03:19:13 +0700 Assertions            PID 74(apsd) Released ApplePushServiceTask "com.apple.apsd-recreatecourierstate-sandbox.push.apple.com" 00:00:10  id:0x0xb00008234 [System: DeclUser SRPrevSleep kCPU kDisp]           2019-06-11 03:19:13 +0700 Assertions            PID 74(apsd) Released ApplePushServiceTask "com.apple.apsd-recreatecourierstate-push.apple.com" 00:00:10  id:0x0xb00008235 [System: DeclUser SRPrevSleep kCPU kDisp]           2019-06-11 03:19:20 +0700 Assertions            PID 54(powerd) TimedOut InternalPreventSleep "com.apple.powermanagement.darkwakelinger" 00:00:15  id:0x0xd00008239 [System: DeclUser SRPrevSleep kCPU kDisp]           2019-06-11 03:19:20 +0700 Assertions            Summary- [System: DeclUser kDisp] Using Batt(Charge: 28)           2019-06-11 03:19:20 +0700 Sleep                 Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=inactive Using Batt (Charge:28%)            2019-06-11 03:19:23 +0700 Wake Requests         [*proc=powerd request=TCPKATurnOff inDelta=43257]            2019-06-11 03:19:23 +0700 PM Client Acks        Delays to Sleep notifications: [com.apple.apsd is slow(2693 ms)]            2019-06-11 15:27:22 +0700 HibernateStats        hibmode=0 standbydelay=0                                                              0              Sleep/Wakes since boot at 2019-06-11 01:52:34 +0700 :0   Dark Wake Count in this sleep cycle:1  Time stamp                Domain                Message                                                                     Duration    Delay      ==========                ======                =======                                                                     ========    =====      UUID: Unknown UUID 2019-06-11 15:27:22 +0700 Failure               Sleep Failure [code:0xFFFFFFFF0000001F]:                                               Sleep/Wakes since boot at 2019-06-11 01:52:34 +0700 :0   Dark Wake Count in this sleep cycle:1  Time stamp                Domain                Message                                                                     Duration    Delay      ==========                ======                =======                                                                     ========    =====      UUID: (null) 2019-06-11 15:27:22 +0700 Start                 powerd process is started                                                              2019-06-11 15:27:22 +0700 Assertions            Summary- [System: No Assertions] Using Batt           2019-06-11 15:27:23 +0700 Assertions            Summary- [System: BGTask] Using AC(Charge: 23)           2019-06-11 15:27:29 +0700 Assertions            PID 54(powerd) Created InternalPreventSleep "Assertion to change proximity monitoring state" 00:00:00  id:0x0xd00008007 [System: SRPrevSleep kCPU]           2019-06-11 15:27:31 +0700 Assertions            Kernel Idle sleep preventers: IODisplayWrangler           2019-06-11 15:27:42 +0700 Assertions            PID 96(hidd) Created UserIsActive "com.apple.iohideventsystem.queue.tickle.4294968779.11" 00:00:00  id:0x0x9000080fc [System: PrevIdle DeclUser BGTask SRPrevSleep kCPU kDisp] 

So, at 3:19 AM the laptop was put to sleep: Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=inactive Using Batt

However 3 seconds later there was a wake request from [*proc=powerd request=TCPKATurnOff inDelta=43257]. Also HibernateStats hibmode=0 standbydelay=0.

I really don’t know that means. Next time I open the lid at 15:27, this was put in log:

UUID: Unknown UUID 2019-06-11 15:27:22 +0700 Failure               Sleep Failure [code:0xFFFFFFFF0000001F]: 

I already disabled Power Nap and Wake for Wifi, tried resetting NVRAM and SMC. Problem still occasionally happen.

Here is pmset -g settings:

System-wide power settings: Currently in use:  standbydelaylow      10800  standby              1  womp                 0  halfdim              1  hibernatefile        /var/vm/sleepimage  proximitywake        1  powernap             0  gpuswitch            2  networkoversleep     0  disksleep            0  standbydelayhigh     86400  sleep                1  hibernatemode        3  ttyskeepawake        1  displaysleep         10  tcpkeepalive         1  highstandbythreshold 50  acwake               0  lidwake              1 

The machine is running latest Mojave 10.14.5.

Tomcat 8.5 running on Ubuntu shutting down when git modifies files in a running context

Having an issue with Tomcat shutting down after a git post-receive hook is triggered and runs the command to checkout a branch (git --work-tree=/opt/myApplication --git-dir=/var/git-data/myApplication.git checkout development -f) to a folder that is being served by Tomcat. I am seeing the following events in the catalina.out log:

25-Apr-2019 15:14:14.360 INFO [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.startup.HostConfig.reload Reloading context [/myApplication] 25-Apr-2019 15:14:14.360 INFO [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.core.StandardContext.reload Reloading Context with name [/myApplication] has started  

It seems odd that it’s attempting to reload the context because I have the option reloadable set to false. The server is running Ubuntu 18.04 with Apache Tomcat 8.5.39. I have the same setup on a RHEL server that doesn’t exhibit this behavior.

Unraid Virtualization: gpu is in use by driver QEMU and Windows 10 “shutting down, reason=destroyed”

I am a total noob to the world of vm but I have gotten past creating an unraid array and I am beginning to create vm’s

My pc contains an i7 8700k, GTX 1080, and a GTX 980 ti.

My problem is that whenever I try to launch a windows vm I created it looks fine until I check out the logs. I keep getting this:

2019-04-23 01:59:46.696+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: Tower 2019-04-23 01:59:46.696+0000: Domain id=1 is tainted: high-privileges 2019-04-23 01:59:46.696+0000: Domain id=1 is tainted: host-cpu 2019-04-23T01:59:46.726907Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) 2019-04-23T02:10:46.942420Z qemu-system-x86_64: terminating on signal 15 from pid 2972 (/usr/sbin/libvirtd) 2019-04-23 02:10:48.343+0000: shutting down, reason=destroyed 2019-04-23 02:12:53.617+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: Tower 2019-04-23 02:12:53.617+0000: Domain id=8 is tainted: high-privileges 2019-04-23 02:12:53.617+0000: Domain id=8 is tainted: host-cpu 2019-04-23T02:12:53.647026Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) 2019-04-23T02:18:55.352186Z qemu-system-x86_64: terminating on signal 15 from pid 2972 (/usr/sbin/libvirtd) 2019-04-23 02:18:56.753+0000: shutting down, reason=destroyed 2019-04-23 02:21:07.385+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: Tower 2019-04-23 02:21:07.385+0000: Domain id=10 is tainted: high-privileges 2019-04-23 02:21:07.385+0000: Domain id=10 is tainted: host-cpu 2019-04-23T02:21:07.414616Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) To me it looks like the startup is attempted many times until it gives me “shutting down, reason=destroyed” if anyone has any experience with this let me know.

My other problem is with my second vm giving me this error code:

PCI device 0000:01:00.0 is in use by driver QEMU, domain Vr Computer 1 My understanding is that because unraid is using my first gpu and not allowing my second vm to use the second gpu in my computer.

If anyone has experience with gpu vm issues help would be much appreciated.

Chitika Is Shutting Down Effectively immediately

Dear Publisher,

After 15+ years in business and millions of publisher relationships, Chitika is hereby shutting down and closing its business. Our sincere thanks to all our publishers with whom we have enjoyed wonderful relationships over the years. We wish you the best of luck and success as you continue to grow your traffic and revenue.

https://virally.site/chitika-is-shutting-down-effectively-immediately/

BIG RIP