Thanks! I didn’t know about
My first attempt went ok with the url. I was thinking to myself, “they’re crazy”. My url is 67 characters long by default generated on github, so how am I supposed to get it down to at most 65? So what I did is I changed and shortened my username to get it to work, but then when I went over stakepool course part dealing with url, I realized how short Carlos’s url was, so I typed in ‘git.io’ which I saw in his shortened url as part of the url name and was able to find “url shortener” tool on git.io and used that to make short url.
I was using a program called timeshift in linux to back up my files so I could return to an earlier working version and start from there instead of installing node from scratch. Well, in my haste to back up one of my sessions, I think I cut the process short of backing up all the files, so when I reinstalled that backup - the one I had worked on the longest - I would occasionally get “ubuntu system problem” messages pop up on my GUI/desktop, which it didn’t have before the backup. So I did a fresh install of Ubuntu from scratch and restarted the course.
Some notes for others reading this thread: if you use github to create your url, and shorten that with git.io, or some other ‘url shortener’, your url will take others to your github page. If you want a ‘website’ looking page with just your ‘pool-related info’ click on the “raw” button to the right, that will generate an url that takes you to a normal looking webpage, then you can shorten that url using git.io. Also, changing the filename of your url has no effect on the hash value of the file…the hashing function used in this instance is only concerned with the contents of the file, not the name of the file itself.
Anyway, Adrem, the biggest problem I’ve had on my second install is that I was accidentally generating errors by having an extra space (having been entered manually accidentally) at the end of a line in my in files to build transactions.
If you use vim and type vim tx.build, for example, it takes you into the file for editing, linux uses special characters which have more than one meaning, like $, ‘space bar to create a single space’, #, etc.
To tell linux you mean to use a regular character reserved for special status as a regular character only, you use the backslash \ before entering that special character of which ‘space bar’ or ‘single blank space’ happens to be a “special character”. Linux sees \‘single space’ and ‘single space’ differently, the latter being a special character and the former just a regular “press of the space bar” or single space. On my edits I discovered that either my file was corrupt or I had corrupted my file because using vim to enter a file to edit it:e.g., ‘vim filename’ will take you into file ‘filename’ to edit it. The files we work on usually look like this:
line one \
line two \
Say represents your cursor position. If you use vim to edit your file and move your cursor through each line it will take you to the last visible character in each line.
So, for each line with backslash, you should see the furthest right you can go is…
line k [\]
where the cursor sits on top of the \ symbol. Check each line by scrolling to the end of the line, if you can go past the end of the line with the cursor, e.g., line k \ then this will generate error(s) when you try to copy, paste and ‘enter’ to run command or run the command through your file as a script by giving it user-executable permissions.
If you notice your command is being split up when pasted, only a few of the last line get processed when you run the command even though you copied all lines, or one of your flags; e.g., --ttl 23442 cannot be found error, then this likely means you have an extra space at the end of one of your lines. Go through each line deleting any extra space at the end of each line and also deleting any extra lines at the bottom of your command and especially deleting any extra lines in the middle of your file.
The above file contains an extra blank line…this blank line appears in vim by not having a tilda ~ symbol for that line;i.e., if you see ~ symbol that means no blanks lines - the end of the file has been reached at the first ~. In this case, you can see there is an extra line after ‘last line’, so get rid of all such “extra lines” in your files so it looks like this…
Extra spaces and lines is where some of my errors came from that were hard to track down. I know extra spaces created errors, but I’m not so sure of extra lines, but I got rid of them anyway because extra lines have a bunch of spaces which linux sees as special characters, which means an extra line might generate errors even though extra line(s) appear after the last line of your command lines.
I still have to set up ufw on my relay and bp. I don’t know if my SPO is working…my block producer is not pulling blocks from IOHK’s relays in LiveView mode. I’ve used internal IPs for my start-up scripts for relay and core as well as for topology files for the relay and core to talk to one another, but not for the IOHK relays in the topology file of the relay…still no blocks showing up. At what point should they show up, do you know? At what point of the process did you get blocks to show up in LiveView if you used that? Mine is always showing 0 blocks. My guess is IOHK’s relays might have trouble finding my core node because my relay host file is using internal IP, but when my relay sends messages to IOHK’s relays even though it’s using an internal IP, IOHK should see external IP with the correct port number 3001 to the relay since routers translate internal IPs to external ones when they go out on the web, so I’m hoping their servers know to respond back on my public IP with the correct port number 3001, so my relay can forward blocks internally to my core node. I think the problem is with my relay’s internal host file. I’ll try changing that.