@Joe-Bishop I increased the FOG Configuration-General Settings-FOG_MEMORY_LIMIT to 1024 and now I am able to list all hosts.
Posts made by Joe Bishop
-
RE: Can not list all hosts after 1.2.0 to 1.3.0 upgrade
-
Can not list all hosts after 1.2.0 to 1.3.0 upgrade
Server
- FOG Version: 1.3.0
- OS: Ubuntu 16.04
Client
- Service Version:
- OS:
Description
Not able to List All Hosts after 1.3.0 update. I am able to search for hosts just not able to list them all. Is there a limit to the number of hosts I can have? I have just over 4500 hosts registered.
-
RE: Organizations Using FOG
Organization: Penn Harris Madsion Schools
Location: Mishawaka, IN
Systems : 4560
Since: 20091 High School
3 Middle
11 Elementary
3 Admin buildingsWe use FOG for all imaging, and for managing network printers.
-
RE: "A valid database connection could not be made"
@Wayne-Workman Thanks for your help. I think that I have it working now. I had to reset the password for remote access. I was able to access it locally, but not from remote.
-
RE: "A valid database connection could not be made"
@Wayne-Workman I have checked all of the passwords and they all match what they are supposed to be as far as I can tell. When these servers were all 1.2.0 they were fine.
-
"A valid database connection could not be made"
Server
- FOG Version: 1.3.0
- OS: Ubuntu 16.04 Storage nodes 14.04
Client
- Service Version:
- OS:
Description
All of my storage nodes have “A valid database connection could not be made” on the FOG Version Information page, and well as on the dashboard. As far as I can tell everything else is working, just wanted to know if there was a way to fix this.
Server
- FOG Version:
- OS:
Client
- Service Version:
- OS:
Description
Server
- FOG Version: 1.3.0
- OS: Ubuntu 16.04 Storage nodes 14.04
Client
- Service Version:
- OS:
Description
All of my storage nodes have “A valid database connection could not be made” on the FOG Version Information page, and well as on the dashboard. As far as I can tell everything else is working, just wanted to know if there was a way to fix this.