2000 PTS - Jenkins Automated Nightly Build Server

[bitbro]

Right now jenkins.bitshares.org loads a page on your server with an iframe inside that loads http://178.63.85.22/

This is a bad way to achieve this. It would be better to let DNS requests to jenkins.bitshares.org be responded by 178.63.85.22 instead of 192.31.186.16.

If you want to stay at the current way of doing it with an iframe, then you have to point the iframe to http://178.63.85.22:8080/ instead of http://178.63.85.22/
Loading http://jenkins.bitshares.org:8080 will try to connect to your server at 192.31.186.16, which won't work.

Ok, great... I didn't realize this is how the web guys hacked it!    I will now slap them upside the face for using such an insane iframe design.   

Thanks

Sent from my iPhone using Tapatalk

[drekrob]

can someone who is having the libcxx issue with bitshares-pts please pm me? I can't reconstruct the problem, so it is hard to debug it.

[bytemaster]

You changed the build directory for keyhotee without telling us or the script. So the script still packaged the binary from the old location. I updated the script, please try the file and tell me, if there is still something wrong with it.
I will look into the issues with libdb packaging for bitshares-pts

Ok... thanks!   Things appear to be functioning and your support is good... sending another 500 PTS while we continue to evaluate the solution.

[drekrob]

I downloaded ftp://178.63.85.22/Bitshares-PTS/MacOS/2014-03-20_00-00-41/BitShares-PTS.dmg and unpacked it. libdb_cxx-4.8.dylib is in there, at the location where it belongs to. If i understand you right, this is the file you downloaded and tried to run and macosx still tries to find the lib on your mac instead of using the supplied one? I'm no expert here, but it looks to me, as if it should work as it is. I will try to find some more information about this topic.

[drekrob]

You changed the build directory for keyhotee without telling us or the script. So the script still packaged the binary from the old location. I updated the script, please try the file and tell me, if there is still something wrong with it.
I will look into the issues with libdb packaging for bitshares-pts

[bytemaster]

I have been evaluating the binaries from genesis.bitshares.org and the Mac Keyhotee Binary (according to Dan N) appears to be exhibiting behaviors of an older version while the BitShares-PTS binary does not properly bundle / link berkley DB.

When I download from genesis.bitshares.org/binaries we get this error:

Process:         BitShares-PTS [36558]
Path:            /Applications/BitShares-PTS.app/Contents/MacOS/BitShares-PTS
Identifier:      org.invictusinnovations.BitShares-PTS
Version:         
Code Type:       X86-64 (Native)
Parent Process:  launchd [191]
Responsible:     BitShares-PTS [36558]
User ID:         501

Date/Time:       2014-03-19 23:24:30.680 -0700
OS Version:      Mac OS X 10.9.2 (13C64)
Report Version:  11
Anonymous UUID:  6A45F32F-8D47-2712-C03F-16050B6168D3

Sleep/Wake UUID: D0F6CF30-420B-490D-B3E4-3485A939AD57

Crashed Thread:  0

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: /opt/local/lib/db48/libdb_cxx-4.8.dylib
  Referenced from: /Applications/BitShares-PTS.app/Contents/MacOS/BitShares-PTS
  Reason: image not found

Binary Images:
    0x7fff6afea000 -     0x7fff6b01d817  dyld (239.4) <2B17750C-ED1B-3060-B64E-21897D08B28B> /usr/lib/dyld
    0x7fff878d5000 -     0x7fff87bd3fff  com.apple.Foundation (6.9 - 1056.13) <2EE9AB07-3EA0-37D3-B407-4A520F2CB497> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff8bfcd000 -     0x7fff8cb43fff  com.apple.AppKit (6.9 - 1265.19) <12647F2F-3FE2-3D77-B3F0-33EFAFF2CEA7> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff9091f000 -     0x7fff9091ffff  com.apple.ApplicationServices (48 - 48) <3E3F01A8-314D-378F-835E-9CC4F8820031> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices

Model: MacBookPro10,1, BootROM MBP101.00EE.B02, 4 processors, Intel Core i7, 2.3 GHz, 16 GB, SMC 2.3f36
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 1024 MB
Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.3f10 13477, 3 services, 23 devices, 1 incoming serial ports
Network Service: Anker USB LAN, Ethernet, en6
Serial ATA Device: APPLE SSD SM256E, 251 GB
USB Device: USB 10/100/1000 LAN
USB Device: USB3.0 Hub
USB Device: USB3.0 Hub
USB Device: My Passport 0748
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: Hub
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
USB Device: USB2.0 Hub
USB Device: Fitbit Base Station
USB Device: USB2.0 Hub
Thunderbolt Bus: MacBook Pro, Apple Inc., 23.4

[bytemaster]

i checked into it and you should be able to login, do you get any message? how does the page behave?

I enter my password then no errors are displayed but it says I am not logged in.

Ok... it seems to work from Chrome.   Safari was having an issue. 

[bytemaster]

i checked into it and you should be able to login, do you get any message? how does the page behave?

I enter my password then no errors are displayed but it says I am not logged in. 

[drekrob]

i checked into it and you should be able to login, do you get any message? how does the page behave?

[bytemaster]

Ok, the domain name situation has been resolved. 

It will not let me sign in and I would like Arlen to be able to admin.   

[BrownBear]

That's odd... no they're from ~20h ago. I'll have to check what's up with that. You can see in the filenames it's march 18th.

EDIT: it was caused by my date formatting gone awry. Fixed it. For some reason bts_wallet didn't get uploaded recently. Seems like the path to the binary was wrong, updating now. https://github.com/InvictusInnovations/keyhotee/commit/f2095166e6270273a967186705d71898b7717e9d this caused the problem afaics.

[bytemaster]

Oh just fyi, we configured our server to respond to jenkins.bitshares.org on port 80 with the jenkins page, so changing the dns setting would already work from our side, since that's what we anticipated. I also added a link to the ptsags website that links to jenkins while this is being fixed, as well as a binaries page that gives you quick access to the most recent binaries:
http://178.63.85.22/binaries/

The newest builds are from Feb 2?

[BrownBear]

Oh just fyi, we configured our server to respond to jenkins.bitshares.org on port 80 with the jenkins page, so changing the dns setting would already work from our side, since that's what we anticipated. I also added a link to the ptsags website that links to jenkins while this is being fixed, as well as a binaries page that gives you quick access to the most recent binaries:
http://178.63.85.22/binaries/

[bytemaster]

Right now jenkins.bitshares.org loads a page on your server with an iframe inside that loads http://178.63.85.22/

This is a bad way to achieve this. It would be better to let DNS requests to jenkins.bitshares.org be responded by 178.63.85.22 instead of 192.31.186.16.

If you want to stay at the current way of doing it with an iframe, then you have to point the iframe to http://178.63.85.22:8080/ instead of http://178.63.85.22/
Loading http://jenkins.bitshares.org:8080 will try to connect to your server at 192.31.186.16, which won't work.

Ok, great... I didn't realize this is how the web guys hacked it!    I will now slap them upside the face for using such an insane iframe design.   

Thanks

[BrownBear]

Right now jenkins.bitshares.org loads a page on your server with an iframe inside that loads http://178.63.85.22/

This is a bad way to achieve this. It would be better to let DNS requests to jenkins.bitshares.org be responded by 178.63.85.22 instead of 192.31.186.16.

If you want to stay at the current way of doing it with an iframe, then you have to point the iframe to http://178.63.85.22:8080/ instead of http://178.63.85.22/
Loading http://jenkins.bitshares.org:8080 will try to connect to your server at 192.31.186.16, which won't work.