Hi,
Following the installation instructions, on a pre-existing Debian (5.0) machine, I got to the backend_info stage and see:
central:~# opsi-admin -d method backend_info
{
"opsiVersion" : "4.0.0.18",
"modules" :
{
"valid" : false
}
}
Any hints?
Anand
why is the backend not valid?
Re: why is the backend not valid?
Hi Anand,
I admit this could be misleading.
It is not your backend that's invalid, it is your modules file. The modules file is a special configuration file used to activate certain cofunding projects.
Opsi does not generate a valid modules file and thus shows the modules as not valid.
This has no impact on the core opsi functionality so you needn't worry about it.
Cheers,
Christian Kampka
I admit this could be misleading.
It is not your backend that's invalid, it is your modules file. The modules file is a special configuration file used to activate certain cofunding projects.
Opsi does not generate a valid modules file and thus shows the modules as not valid.
This has no impact on the core opsi functionality so you needn't worry about it.
Cheers,
Christian Kampka
opsi support - uib gmbh
For productive opsi installations we recommend support contracts.
http://uib.de
http://opsi.org
For productive opsi installations we recommend support contracts.
http://uib.de
http://opsi.org