Local

Remote

Switch to Shell:

1. Connect USB keyboard to terminal.
2. Press Control + Alt + F1.
3. At the login: prompt, type root and press Enter.
4. At the Password: prompt, type #FullCount#Support# and press Enter.

**Note: @11ianc3 is the password before OS version 6.0.0.

1. Log in via SSH.
2. At the command prompt, type chvt 1 and press Enter.

Shell access will allow the user to execute commands from the command-line-interface. Implementers onsite at a community will want this for various reasons, mostly network testing related. It's preferred that FC support performs these tests via remote connection, however, there are times where that isn't possible and a customer can be walked through this as a last resort.

Switch to Application:

1. At the command prompt, type “exit” and press Enter.
2. Press Control + Alt + F7.

1. Log in via SSH.
2. At the command prompt, type chvt 7 and press Enter.

This is used to bring you back to the application without rebooting.

Switch to Support Information:

1. Connect USB keyboard to terminal.
2. Press Control + Alt + F9.

1. Log in via SSH.
2. At the command prompt, type chvt 9 and press Enter.

This page reveals the network information the device is currently using which is incredibly helpful whent troubleshooting a device that cannot be connected to remotely. Use this to find:

• Serial Number
• OS Image Version
• MAC Address
• Subnet Mask
• IP Address
• Default Gateway
• DNS Servers

Network communication test:

1. Switch to shell.
2. At the command line, type ping followed by an argument that would either be a domain or IP address.

1. Log in via SSH.
2. At the command line, type ping followed by an argument that would either be a domain or IP address.

ping is a basic network communication test that can be used to gauge how well two hosts can communicate with each other. Pinging portal.fullcount.net (cloud-hosted domain) or the on-premise server's domain can help the user understand how well the application is performing on the device depending on what percentage of packets reach its destination and back as well noticing how long it takes for that trip to be finished. Pinging the IP address of a printer or POS device can help the user understand whether the host is reachable at all.

Display MAC address of recently pinged device:

1. Switch to shell.
2. At the command line, type arp -n.

1. Log in via SSH.
2. At the command line, type arp -n.

The arp command displays a device's ARP table which contains the MAC addresses of devices on the local network that have been pinged recently. This table contains recent data and cannot be leveraged reliably without initaiting recent ping tests before it.

Resolve a domain:

1. Switch to shell.
2. At the command line, type nslookup followed by the domain you'd like to resolve.

1. Log in via SSH.
2. At the command line, type nslookup followed by the domain you'd like to resolve.

This is a DNS test. If a device cannot resolve portal.fullcount.net (cloud-hosted) or the on-premise server's hosted domain using its primary DNS server then you can expect application issues.

Establish SSH tunnel to a local POS device:

1. Switch to shell.
2. At the command line, type ssh followed by the IP address of the Linux POS device you'd like to get into.

1. Log in via SSH.
2. At the command line, type ssh followed by the IP address of the Linux POS device you'd like to get into.

Ideally you'd establish your SSH tunnel to a device via Device Management, however, there are corner-cases in FC support where you may find it useful to SSH into a device from another device. A common reason this could occur is if the port the problem POS device is using is not configured like the rest of the working devices' ports are.

Reboot the device:

1. Switch to shell.
2. At the command prompt, type reboot.

1. Log in via SSH.
2. At the command prompt, type reboot.

If the situation calls for a hard reset of the device itself rather than just the application then the reboot command is convenient. Any OS or non-application changes to the devices should be rebooted ensure the device boots correctly post-change.

Configure a Static IP Address for <7.3.0:

For 7.3.0+

1. Connect USB keyboard to terminal.
2. Press Control + Alt + F1.
3. At the login: prompt, type networkconfig and press Enter.
4. At the Password: prompt, type networkconfig and press Enter.

1. Log in via SSH.
2. At the command prompt, type yast lan, and press Enter.
3. Select the network card you want to configure. Press Alt + i to edit settings for this card.
4. Press Tab to highlight “Statically assigned IP Address”, and press Spacebar.
5. Press Tab to highlight “IP Address”.
6. Type in the IP address and press Tab to highlight “Subnet Mask”.
7. Type in the Subnet mask and press Alt + N.
8. Press Alt + u to set the default gateway.
9. Type in the default gateway and press Alt + s to set up your DNS servers.
10. Press Tab to highlight “Name Server 1”.
11. Type in the IP address of the DNS server,
12. If necessary, press Tab to highlight “Name Server 2”, and type the IP address of the secondary DNS server.
13. Press Alt + O (capital ‘o’) to save and apply your changes.

FullCount prefers the hardware is configured DHCP, however, a customer's network may require a static IP address to be configured to a device. This should only be performed on a wired terminal or print server/KDS unit.

Stop Application:

1. Switch to Shell.
2. At the command prompt, type systemctl stop posapp and press Enter

1. Log in via SSH.
2. At the command prompt, type systemctl stop posapp and press Enter

On devices 7.1.0 and newer, you will need to stop the application before you restart the application.

Restart Application:

1. Switch to Shell.
2. At the command prompt, type systemctl restart display-manager and press Enter.

1. Log in via SSH.
2. At the command prompt, type systemctl restart display-manager and press Enter.

A fresh restart of the application is useful if you know a networking issue has occurred and you'd like to refresh the screen without a full reboot.

Restart FullCount Service:

1. Switch to Shell.
2. At the command prompt, type systemctl restart fullcount and press Enter.

1. Log in via SSH.
2. At the command prompt, type systemctl restart fullcount and press Enter.

Restarting the FullCount service is a bit of a shot-in-the-dark when troubleshooting application issues. You wouldn't really know that you should do this step without the assistance of a tech team member, however, it's simple enough to do it anyway if you're looking for a fresh application session. You'd typically restart the application after restarting the service.

Printing protocols test:

1. Switch to Shell.
2. At the command line, type netcat -vz followed by the IP address of the printer you're testing a connection with. The IP address should be followed by 9100 if it's a network printer or 22 if it's a terminal printer.

1. Log in via SSH..
2. At the command line, type netcat -vz followed by the IP address of the printer you're testing a connection with. The IP address should be followed by 9100 if it's a network printer or 22 if it's a terminal printer.

Port protocols can be thought of as "tunnels" in a network that information travels through. Ports 9100 and 22 are used for various printing processes in FullCount and if blocked can cause trouble. netcat is used to test these ports.

Display Wireless Network Settings (<7.3.0):

1. Switch to Shell.
2. At the command prompt, type cat /etc/sysconfig/network/ifcfg-wlan0 and press Enter.

1. Log in via SSH.
2. At the command prompt, type cat /etc/sysconfig/network/ifcfg-wlan0 and press Enter.

Check a device's SSID and password for the wireless network.

Display connected USB devices:

1. Switch to Shell.
2. At the command line, type lsusb.

1. Log in via SSH.
2. At the command line, type lsusb.

The All in One terminal's receipt printer is connected via USB so this command can be used to check that connection. This probes all USB devices though including barcode scanners, RFID readers, cell phones, etc.

Determine which OS image is installed:

1. Switch to Shell.
2. At the command line, type find / -name 'boot.kiwi' | xargs cat | grep -i 'image description'

1. Log in via SSH.
2. At the command line, type find / -name 'boot.kiwi' | xargs cat | grep -i 'image description'

FullCount supports hardware where a single model may have one of multiple possible images installed or may have a non-specific serial number convention. This command allows you to punch in an image description and searches a notable Kiwi file that would contain this information. Examples of valid image descriptions: egalax, 3m, kitchen, print server. If the command gives you no output then the string you entered is not in the OS image description (therefore not the OS image you searched for).

Enable mouse pointer (7.3.1+)

1. From the GUI, press "Alt+m"

Print servers and KDS do not typically have a touchscreen, so setting up interfaces statically using NetworkManager is difficult. This make the mouse appear on the screen so a user can use a USB mouse.