Getting Site ID is missing from session data! error when trying to log into OpenEMR

[hcrossen (HENRY V CROSSEN)]

I’m getting “Site ID is missing from session data!” error when trying to log into OpenEMR. I was able to log in this morning as well as one of my employees and we are able to still access OpenEMR and it is functioning normally. However the staff at my other office (who tried logging in later) as well as when I tried logging in on another PC at my office, cannot.

EDIT: We can get to the login screen, the error pops up upon attempting to log in.

Update: And just now I can’t login either.

I checked in AWS Console and everything appears to be running just fine. Certificates are all valid.

OpenEMR Version
I’m using OpenEMR version AWS Cloud Standard

Browser:
I’m using Chrome.

Operating System
I’m using Windows 10 and Chrome OS

Logs
I saw nothing in the logs.

[JXPrime (Jonas Bush)]

I can see inside the globals.php file, there is this code:

But I’m not super versed on PHP and don’t know what is going on here.

Jonas

[brady.miller]

Hi @hcrossen ,
That is a catchall error that generally catches underlying session issues in the platform. Rec:

1. Remove browser cookies
2. If still not working, restart the server
3. If still not working, then see if anything is going to the javascript console (chrome browser->more tools->developer tools->console)

[JXPrime (Jonas Bush)]

Hey Brady, I’m helping Henry out with his site administration…I have tried all of those things and don’t see anything pertinent. Nothing in the js console, I see 1 cookie being set, but removing that ends up w/ the same result.

[JXPrime (Jonas Bush)]

I also see this in /var/log/apache2/error.log:

[JXPrime (Jonas Bush)]

And doing a couple of df’s seems to confirm this?

Have we run out of space in our AWS EC2 size?

[brady.miller]

yep, that appears to be the case. That also makes complete sense since saving sessions in php also requires space (not being able to save breaks lots of things, but will be a good thing for the project to keep in mind in future when folks report this issue).

[JXPrime (Jonas Bush)]

you don’t have any guidance or a link to any guidance on how to expand that available space by chance, do you?

[brady.miller]

It’s been while for me, but dug up this post from awhile back:

Clarification on AWS cloud storage sizes

Hi, @sjpadgett , just give it time and docker will win you over @juggernautsei, on aws, you can both upgrade instance and increase the drive size (just need to shut down instance first): https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html https://www.serverkaka.com/2018/12/how-to-increase-ebs-volume-size-of-aws-instance.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+serverkaka%2FOkhb+(Linux+System+Administration) -brady

[JXPrime (Jonas Bush)]

Yup, that seemed to do it. Thanks!

[JXPrime (Jonas Bush)]

Ok we ran into this issue again, but now in the EC2 console it seems like the docker drive is full and I don’t see how to extend that drive:

[stephenwaite]

hi @JXPrime , isn’t it at the bottom of that article Brady shared above?

[JXPrime (Jonas Bush)]

So we increased the size of both volumes on the EC2 instance to 30GB, but I don’t see that size showing up for the docker volume when I run df -h. (dev/xvdd). I’m a bit out of my depth when it comes to Linux/Docker stuff so I’m stumbling through as best I can.

To get my friend up and running, I just deleted the 18GB! access.log file.

[stephenwaite]

here’s that relevant part to resize those, the device names differ from your above posting of course