On May 16, 5:12 pm, Jason Grout <[email protected]> wrote:
> kilucas wrote:
>
> > On May 12, 6:50 pm, Jason Grout <[email protected]> wrote:
> >> kilucas wrote:
>
> >>> On May 12, 5:14 pm, Jason Grout <[email protected]> wrote:
> >>>> kilucas wrote:
> >>>>> <snip>
> >>>>> I hadn't thought about multiple v single notebook architectures and
> >>>>> will think harder about that now.
> >>>> Or what I would do in your place is just use one notebook for now, and
> >>>> worry about trying to set up multiple notebooks later if you want it.
> >>>> It's trivial to start up multiple notebook instances once you have one
> >>>> working.
> >>> V helpful. Thanks.
> >>>>> So do I just set up the server by following the single user
> >>>>> installation instructions plus your tips on security, and then find a
> >>>>> URL that provides remote access to that server? (And if so, what would
> >>>>> that URL look like?)
> >>>> There is one setting that you need to change on the vmware server to
> >>>> allow outside network access (someone else will have to chime in here; I
> >>>> don't know the setting). I believe you need to change the networking to
> >>>> be "bridged networking". Then you need to work with your network
> >>>> administrator about the URL to use to access the server.
> >>> I'll go in search of this setting. Effectively I am the administrator
> >>> here (not that I'm a professional techie) so I know the external URL
> >>> to the current web server that's running on my Windows server but I
> >>> don't know how I'd adjust this to find Sage. Maybe that'll become
> >>> obvious but if anyone knows what shape the URL should take, I'd be
> >>> interested to hear. I'm not even clear at this stage which web server
> >>> (my existing server or one supplied by Sage) will apply.
> >> The vmware sage server will have its own IP address, and thus its own
> >> hostname and URL. Sage includes a webserver that will run over the
> >> vmware network address; that is the webserver you would use (not the one
> >> on the host computer). If you change the networking to bridged
> >> networking, start up the vmware server, then start up sage, you can get
> >> the hostname by doing:
>
> >> sage: import socket
> >> sage: socket.getfqdn()
> >> 'good'
>
> >> (fqdn stands for fully qualified domain name)
>
> > Can I just clarify at what point I run this please? (I'm not quite
> > sure when I've "started sage" and when I haven't)
>
> > - If I run it after starting the VMWare Player and the sage_vmx so
> > I'm, at the Sage Login prompt then I'm told that I'm logging in
> > incorrectly when I try the "import socket" command.
> > - If I start the VMWare Player, open the sage_vmx and run the notebook
> > command first, and then try the above commands, I'm still told I'm
> > logging in incorrectly.
> > - If I start the VMWare Player, open the sage_vmx, login to sage
> > (whether I run the notebook command first or not), the import socket
> > command is greeted with "import: unable to open X server <followed by
> > two single quotes>"
>
> > In all these cases the networking was nominated as "bridged" before
> > opening the VMWare Player.
>
> > At present I can't tell if I'm doing this at the wrong poin t in the
> > starting and logging in sequence or whether I'm doing it at the right
> > time but something's not working as planned. S I hope you might be
> > able to clarify for me.
>
> Good job on being so persistent. As you work through this process, we
> are also realizing things that may make it easier for those following
> after you.
I'm just grateful for the help - sorry to be so pesky. Mind you,
William's beginning to flag that I may be suffering from the binary/
cpu incompatibility problem so my efforts may prove forlorn.
>
> Anytime you see a line that starts with "sage: ", that means to start
> Sage up first, then type in the command following the colon.
Very helpful confirmation, though I continue to get confused about
which stage among the various steps constitutes "starting sage". In
the sequence below, which one is the point where sage is "started"?
1) Running the VMWare Player from Windows [I presume sage isn't
started by the end of this step]
2) Opening sage_vmx in VMWare Player and reaching the login menu
beneath 4 options (notebook, off, manage, sage) [As I ran a thing
named sage this might mean I've started it but the description of the
next step might also be a candidate]
3) Typing "notebook" (which actually means logging in as "notebook
with a null passowrd if I understand correctly). [As notebooks seem to
be the operational part of Sage, maybe I have to have done this step
to have "started" sage. But I don't seem able to type any maths at
this point so perhaps a further step is needed before I've "started
sage"]
4) Either reaching the command line (I haven't found out how to do
this successfully) or opening a page in Firefox that corresponds to
one of the page types on www.sagenb.org (these options could include a
login page, a home page that lists some worksheets, or maybe I'd
arrive at a specific worksheet. As I haven't managed to reach this
point successfully I don't know what I should see) [This might be the
stage at which I can type some maths so maybe this corresponds to
"starting" sage]
>
> Hmmm...I didn't try the above commands in a vmware system. It's
> possible that there is something that is not installed on the vmware
> system that prevents the command from working.
>
> Another way to get the same information is to login as "manage", then
> type "hostname". You can also type the command "ifconfig" and it will
> give you a bunch of information about all the networking on the vmware
> system, including your IP address, etc. The IP address is the address
> following the " inet addr:"
I logged in as "manage" and the hostname responded with "sage". So
presumably "sage" is my hostname.
I tried http://sage and http://sage:8000 in Firefox started from
Windows (not from within VMWare) but these took me to www.sage.com,
the home page of a well known seller of mid-market financial software.
Should I have seen something to do with our sage or are these URLs
irrelevant?
I ran ifconfig in VMWare Player while logged in as "manage" (in fact I
assumed it was a typo and should have been like the Windows command
ipconfig at first) and did indeed see some IP details. The indet addr
line showed 192.168.229.128. I therefore tried to reach http://192.168.229.128
and http://192.168.229.128:8000 in Firefox within Windows. Firefox
continues to throw an error saying the site seems valid but the
browser couldn't establish a connection.
Should I have seen something to do with sage or are these URLs
irrelevant.
I can't ping sage from windows or while logged in to "manage" within
VMWare Player. Is that significant?
I also checked what Windows thinks about the IP settings using
ipconfig /all from Run | cmd. After all, I'm running Firefox from
Windows. It shows a similar IP address of 192.168.229.1 associated
with VMNet8. My VMWare Player's networking is set to NAT and
vmconfig.exe shows VMNet8 relates to NAT and that it uses the subnet
192.168.229.0. But, if I point Firefox at http://192.168.229.1 I'm
asked to log in to something via a login box (not a web page with
login fields on it). I don't know what to put into these (neither
login/sage nor my normal windows login credentials works).
Should I reach such a login dialog and if so what do I enter?
Attempts to reach http://192.168.229.1:8000 fail again with a message
that the site seems valid but Firefox couldn't establish a connection.
So is any of this hopeful or is it all just irrelevant noise generated
by an incompatible binary and CPU?
Thanks
Kevin
>
> Thanks,
>
> Jason- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
