Hi Marcin,
On Mon, May 16, 2016 at 5:51 PM, Marcin Stolarek <[email protected]> wrote: > 2016-05-14 16:49 GMT+02:00 Raymond Wan <[email protected]>: >> Anyway, after upgrading the OS, something strange happened. The queue >> failed to start and I got error messages in the log about the >> RealMemory being insufficient. I ran "slrumd -C" again, and the value >> of RealMemory changed! For example, from 32058 to 32057. So...I >> changed it in slurm.conf and restarted slurm and all is fine now. >> >> But, I was wondering ... is this something I should be alarmed about? >> How could I "lose" memory during an OS upgrade. Is it an >> approximation and there is some kind of rounding error? >> >> Ray > > > > It looks like this value comes from get_memory function: > https://github.com/SchedMD/slurm/blob/9d5ad6398b85c185756f93b44efbc4fbab028c81/src/slurmd/slurmd/get_mach_stat.c > > The actual source (if you check the code) can be _system_configuration, or > _SC_PHYS_PAGES or hw.physmem. I think that upgrading your OS caused for > example sys/systemcfg.h library installation or removal, which in fact > changed the source of the information and.. that's why the number changed. Thanks a lot for finding the place in the source code! I have to admit that I find SLURM's source code to be a bit intimidating and never had the courage the look through it myself. (Nor do I have the expertise to know I've found what I'm looking for...) I'm relieved that my system isn't mysteriously losing memory with the upgrade -- thanks a lot for your reply! Ray
