Regarding the low bandwidth and a low number of connections, this could be typical for a new relay. Reference https://blog.torproject.org/blog/lifecycle-of-a-new-relay

> [ARM NOTICE] Read last day of bandwidth history from state file

> (-7502 seconds is missing)

This is normal in my experience. Arm is trying to read your node's bandwidth history to populate the graphs with data collected before you started Arm. I don't know why it fails, but you can squelch it by adding the following config line to ~/.arm/armrc (or wherever you keep your armrc file):

  features.graph.bw.prepopulate false

> [ARM WARN] The torrc differs frm what tor's using.  You an issue a

Pretty much what it sounds like; you edited torrc after starting up Arm. To bring in the chages such that Arm is in sync, just press 'x' in Arm twice and it will issue a HUP signal to the Tor process, which reloads the config.

> [ARM NOTICE] Tor is preventing system utiliites like netstat and lsof

You need to add the following to /etc/tor/torrc if you want to utilize all the features of Arm:

  DisableDebuggerAttachment 0

It's disabled by default for security (with a value of '1'), so think carefully before doing this. It "reduces security by enabling debugger attachment to the Tor process. This can be used by an adversary to extract keys." (Quoting from https://trac.torproject.org/projects/tor/ticket/13880). If you do enable the deubgger attachment for Arm, make sure your control port is locked down (not reachable from the Internet or from other hosts you don't control, etc.)

It does seem a little odd you're still at 0 bandwidth with no connections. Without more data, it's hard to say what else might be going wrong (if anything). What does /var/log/tor/log have to say? There should be some lines in there that indicate if it's reachable from the internet.