Basically, when I restart my server, half, some or most of the illuminated panels I'm using for lighting forget to emit light until I destroy one (or all) of them in the affected areas.

Currently running rv4 Alpha 7 on Forge 2166.

There isn't a crash log or anything else that I can provide other than screenshots showing the issue.

Is this a single chunk?

No. It's across multiple chunks. Pictures 1 and two are on two opposite sides of the room. Certain spots between were out (like just 1 or 2 lights vs a whole area as represented above. I can show you more specifically with more screenshots... just would need to restart the server again.

Each one. With the angle it is hard to tell, but it really looks about 16 block long and the square shape really makes no sense with normal lighting behaviour. Like it actually looks like a single chunk did get reset somehow.

If it is reproducible, please provide a full server log. It might contain some error entries,

Recorded two videos with the chunk map up showing a minor case and after restarting the server, it was a major case.

Video 1: https://www.youtube.com/watch?v=vDXb6umYM4Y
Video 2: https://www.youtube.com/watch?v=w6_5u_5DycY
first vid logfile.txt
second vid logfile.txt

I'm also attaching the client logfile (did not restart client b/t server restarts). Also, this only shows up after a server restart.
fml-client-latest.txt

Would like to add that YES the server really thinks there's no light in those areas. Just had two creepers spawn and blow up on me while I was working on patterns.

Would like to give another update. Just updated to the latest version of AE2 (Alpha 9) on forge 2185 and the same thing happens.

Did you know that there is a Vanilla lighting glitch that occasionally chunks will NOT light up properly, and to fix this error you can simply place a block that emits light and the glitch is fixed? This is likely NOT your issue, but I am just throwing that out there.

Yeah, after watching those videos, I kinda think that the error is actually not AE2, but actually Minecraft itself. I can replicate this error myself without ANY mods, but I mostly see this around lava pools in unloaded chunks. It is a chunk loading error, and there isn't anything AE2 DEV's can do about it.

Hey! You know how I said that I could replicate this glitch in vanilla? Well, I just did. I was mining along in survival and came to an unloaded lava pool. Here are the pictures.




The 4th image is after I updated the chunk.

Ok, that's all fine... but this doesn't change the fact that regular torch lighting NEVER does this. Whatever type of light AE2 provides seems to be the type that bugs out on server reboots. Why cant it be changed to match the way a torch works so that this does not happen? Torches never have this problem. Also, if that's not an option, cant the AE2 controller send out a chunk 'ping' or something that forces the entire AE2 network to respond on world initialization thus making sure that all chunks associated with the AE2 network are refreshed to prevent this from happening? I'm sure that with a little creativity, this can easily be fixed.

To be honest, I was thinking that if AE2 is causing this problem in it's own unique way, that it is missing a function that, like you said, checks all lighting objects connected to AE2 Systems. I doubt that is the issue, but If it is, the solution should just be as simple as adding a few lines of code for checking light sources. The fact that it is repeating is curious, but is not unheard of to me.