This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
Neels Hofmeyr gerrit-no-reply at lists.osmocom.orgReview at https://gerrit.osmocom.org/2837 OsmoGSMTester: tweak sysmobts: systemctl, ssh, limits, reboot Simpler systemctl rule to disable stock services. Fix the limits config, which was not the right way for sysmoBTS. SSH access: apparently no need to create an ssh key at all, login is permitted right away. Add hint to reboot at the right time. Change-Id: I8e686383318ee2eece908a4e690e5061ade0cd02 --- M OsmoGSMTester/chapters/install.adoc 1 file changed, 28 insertions(+), 37 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/37/2837/1 diff --git a/OsmoGSMTester/chapters/install.adoc b/OsmoGSMTester/chapters/install.adoc index 9900e6b..41c85e4 100644 --- a/OsmoGSMTester/chapters/install.adoc +++ b/OsmoGSMTester/chapters/install.adoc @@ -530,10 +530,7 @@ be disabled: ---- -systemctl mask osmo-nitb -systemctl mask sysmobts -systemctl mask sysmopcu -systemctl mask sysmobts-mgr +systemctl mask osmo-nitb sysmobts sysmopcu sysmobts-mgr ---- This stops the stock setup keeping the BTS in operation and hence allows the @@ -563,46 +560,40 @@ You may set the name server in '/etc/resolve.conf' (most likely to the IP of the gateway), but this is not really needed by the osmo-gsm-tester. -==== SSH Access - -Copy an SSH public key from the system/user that runs the osmo-gsm-tester, -presumably user 'jenkins' on the *main unit* (not from the jenkins master!), to -the 'authorized_keys' file of user 'root' on the SysmoBTS. - -If the 'jenkins' user on the *main unit* has no key pair yet, generate one -first, with an empty passphrase: - ----- -ssh jenkins at my_main_unit -ssh-keygen ----- - -Then copy the public key to the SysmoBTS: - ----- -ssh jenkins at my_main_unit -cat ~/.ssh/id_rsa.pub -# copy this public key ----- - ----- -sysmobts=root at 10.42.42.114 -ssh $sysmobts -cat id_rsa.pub >> ~/.ssh/authorized_keys -# paste above public key and hit Ctrl-D ----- - ==== Allow Core Files In case a binary run for the test crashes, a core file of the crash should be -written. This requires a limit rule. Copy the following config file from the -osmo-gsm-tester source tree to the SysmoBTS: +written. This requires a limits rule. Append a line to /etc/limits like: ---- -sysmobts=root at 10.42.42.114 -scp install/osmo-gsm-tester-limits.conf $sysmobts:/etc/security/limits.d/ +ssh root at 10.42.42.114 +echo "* C16384" >> /etc/limits ---- +==== Reboot + +Reboot the BTS and make sure that the IP address for eth0 is now indeed +10.42.42.114, and that no osmo* programs are running. + +---- +ip a +ps w | grep osmo +---- + +==== SSH Access + +Make sure that the jenkins user on the main unit is able to login on the +sysmoBTS, possibly erasing outdated host keys after a new rootfs was loaded: + +On the main unit, for example do: + +---- +su - jenkins +ssh root at 10.42.42.114 +---- + +Fix any problems until you get a login on the sysmoBTS. + [[hardware_modems]] === Modems -- To view, visit https://gerrit.osmocom.org/2837 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: newchange Gerrit-Change-Id: I8e686383318ee2eece908a4e690e5061ade0cd02 Gerrit-PatchSet: 1 Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Owner: Neels Hofmeyr <nhofmeyr at sysmocom.de>