On May 26, 2011, at 10:10 PM, harry smythe wrote:
> Hello,
>
> Please excuse my very limited technical knowledge.
>
> I'm running Mac OSX 10.5.8 with 2 GB RAM and Firefox 4.0.1 on a Macbook. My
> JavaVM seems to be 12.8 and I can't find a newer one for Mac.
Mac OS X 10.5 has Java 1.5 installed by default, which is what Freenet
requires. If you want to check for yourself you can type "java -version" into
the command line.
> Up until Freenet 0.7.5 Build #1372 build01372, Freenet-ext Build #26 r23771,
> I had no problems. Normally, I would install the Mac version from the
> "downloads" webpage, or use the offline installer for Linux. Either worked
> well. IZPack install always took the browser to 127.0.0.1:8888/wizard. Using
> the line command "status", I could see:
> "macbook:*** ***$ ./run.sh status
> Freenet 0.7 is running (10433)."
>
>>
> With all the updated install programs after build #1372, the installs would
> seem to finish, but the browser at 127.0.0.1:8888 wouldn't launch, or if it
> did, it would show:
> "Unable to connect, Firefox can't establish a connection to the server at
> 127.0.0.1:8888."
> Double-checking through Terminal with the line command "status", I could see:
> "macbook:*** ***$ ./run.sh status
> Freenet 0.7 is running (6006).
> macbook:*** ***$ ./run.sh status
> Freenet 0.7 is not running."
> From "running" to "not running" takes about 8-10 seconds.
You really, *really* shouldn't be upgrading Freenet by downloading and
re-installing it. Updating should be a painless procedure. Depending on the
setting you chose when you first set up your node, it will either auto update
or ask you to update when a new version is released.
You might not be able to connect to 127.0.0.1:8888 because you had not shut
down Freenet properly before you installed the new version directly over the
old version. That means that port 8888 is still being reserved for the old (now
defunct) process. In my experience for that situation, Freenet will simply use
the next available port (usually 8889). Why not try connecting through that?
> For some weeks, I offline-installed build 1372 for Linux, had no problem with
> the browser interface, waited for a few connections (2/40 connections after 2
> hours) and for the "update" button to appear on the 127.0.0.1 webpage.
> (Without connections, that update option isn't available.) This was slow but
> seemed to work after some time.
2 connections after 2 hours? That can't be right. I've always gotten a minimum
of 10 connections after 30 or so minutes of uptime.
Admittedly I am not familiar with the Linux installer, but you shouldn't be
using it when you're running Mac OS X.
> Now, 1372 still installs but can't make any connections at all, in any amount
> of time. So I can't use that method any more. The 1376 webpage jnlp installs,
> but line command "status" shows that the program stops after some seconds
> (resulting in Firefox's "unable to connect" message, I guess), as do all the
> Linux offline installers after 1372.
That's odd. Have you checked the log files to see what might be causing it to
shut down like that?
> After a 1372 install, a line command called ",/update.sh start" seems to show
> all kinds of downloading and installing of jars and ext-jars, but the updated
> program still dies after about 8 seconds.
What program are you referring to that dies after 8 seconds? Freenet, or the
update.sh script? If you mean running update.sh only lasts 8 seconds, then I
would expect that means that it quickly checked and found that everything was
updated.
> So with a 1372 Linux offline installer, I can install and get a browser
> interface because it continues to run but cannot connect to others. With any
> of the updated installers, I can install, but get no browser interface,
> because the program seems to die too soon, I guess.
AFAIK the Linux version might not be able to make any connections because some
part of the install is incompatible with Mac OS X. After doing a clean install
of the Mac version, try my suggestion above to try connecting to 127.0.0.1:8889
and consecutively higher ports. I would suggest keeping a copy of the log files
of any installs you currently have, as they may prove useful.
Hope this helps,
Daxter
_______________________________________________
Support mailing list
[email protected]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[email protected]?subject=unsubscribe
