[Support] Djoss - CrashPlan PRO (aka CrashPlan for Small Business)


1020 posts in this topic Last Reply

Recommended Posts

Noticed that my CPUI was getting hammered this evening, and it looks like CrashPlan is the culprit. It's currently backing up my ~26GB CA Backups appdata.tar.gz file (which it reckons will take 3 days...). This isn't the first time that that file is backed up, but I've never noticed such a spike in CPU usage? Any ideas what could be up?

I heard that maybe not enough RAM allocation can spike CPU so I added the env var for 4096M (as well as via the Crashplan command line), but it still seems to be hitting my CPU harder than I've seen before (while also only using 1.5GB RAM).

Any idea why? Is it common for large single-files to cause this and I've just never noticed before, or is something problematic going on?

Thanks for your help and experience.

Link to post
  • Replies 1k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Yes, I will provide a new image with the new CrashPlan version integrated.   Thanks for reporting this.  This is currently the most efficient wait for me to know there is a new CrashPlan ver

Support for CrashPlan PRO (aka CrashPlan for Small Business) docker container   Application Name: CrashPlan PRO (aka CrashPlan for Small Business) Application Site: https://www.crashplan.com

I think this is related to the "official" way to use CP on a headless computer:   https://support.code42.com/CrashPlan/4/Configuring/Use_CrashPlan_on_a_headless_computer   Not sure

Posted Images

On 3/11/2021 at 6:54 PM, jademonkee said:

Noticed that my CPUI was getting hammered this evening, and it looks like CrashPlan is the culprit. It's currently backing up my ~26GB CA Backups appdata.tar.gz file (which it reckons will take 3 days...). This isn't the first time that that file is backed up, but I've never noticed such a spike in CPU usage? Any ideas what could be up?

I heard that maybe not enough RAM allocation can spike CPU so I added the env var for 4096M (as well as via the Crashplan command line), but it still seems to be hitting my CPU harder than I've seen before (while also only using 1.5GB RAM).

Any idea why? Is it common for large single-files to cause this and I've just never noticed before, or is something problematic going on?

Thanks for your help and experience.

FYI: I think it was just related to that one large file. CPU utilisation has returned to normal now that it's finished uploading it (and it didn't take 3 days, either). I guess I've just never noticed the CPU usage before in the 4 or so years of using CrashPlan + CA Backups

Link to post

Thanks again for this docker and the work done here.

I have receievd a message saying my system has not been backed up for a few days. I have gone into the web ui for crashplan and can see an update is availble but the system is unable to download the update. I have tried several times and waited a few hours but no joy.

I have checked and the docker syas it is up to date....

I am not seeing anything useful in the logs?

How do I update to the latest version of Crashplan? The one ithe WebUI is telling me to update to? The docker says it is current.

I am hoping this will fix the communication and backup issue? THanks!

Link to post
59 minutes ago, TexasDave said:

Thanks again for this docker and the work done here.

I have receievd a message saying my system has not been backed up for a few days. I have gone into the web ui for crashplan and can see an update is availble but the system is unable to download the update. I have tried several times and waited a few hours but no joy.

I have checked and the docker syas it is up to date....

I am not seeing anything useful in the logs?

How do I update to the latest version of Crashplan? The one ithe WebUI is telling me to update to? The docker says it is current.

I am hoping this will fix the communication and backup issue? THanks!

Exactly the same situation here, I think an update of the container is required with the latest version of CrashPlan.

Link to post

I see the update notification, too, but my backups are working fine, so I don't think the update is related to your backups not working.

Did you update your account to use 2FA? They made that a requirement as from March 4, so maybe that's it.

Here's how to set it up: https://support.code42.com/Small_Business/Get_Started/Two-factor_authentication_for_CrashPlan_for_Small_Business

 

(note that 2FA isn't needed when logging into the UI: only for the dashboard on the web)

 

And yes: the update is tied to the Docker image, so we'll have to wait for it to be updated by @Djoss

Link to post

Others are saying 2FA has not affected anything for the docker (including the developer, DJoss).

I do have 2FA but can log in with no issues to the Docker UI.

I also updated to 9.6.1 and I think the reboot to the new OS may have triggered this as well? So new OS, new Crashplan, 2FA, etc - could be numerous things?

Thanks!

Link to post

Yes, I will provide a new image with the new CrashPlan version integrated.

 

Thanks for reporting this.  This is currently the most efficient wait for me to know there is a new CrashPlan version available :)  

  • Like 2
  • Thanks 2
Link to post

I have activated 2FA a few weeks ago, without any impact on the backup process in the container, and I've been under Unraid 6.9.0 beta35 for around 4 months, so no OS version change here.

I just had a closer look at the backup history, it fails to update to the latest version, which is normal, and retries every hour, but backups are indeed working. The files modified today can be restored from the cloud, either from the container or the webadmin interface. So, I think the alert mail we have received with @TexasDave is more about the update fails than backup fails.

As a reminder, the number of days after which you receive a warning email is a parameter which can be set in the webadmin interface. It's 2 days for me, but I think I have shortened it from 7 days to 2 days when I installed the container. That may explain why others haven't received -yet- these emails.

Link to post
14 hours ago, Djoss said:

Thanks for reporting this.  This is currently the most efficient wait for me to know there is a new CrashPlan version available :)  

 

I can get you another copy of the TPS report.  haha joking.

DJoss - thanks for your support on this container.

Link to post

This app has worked great for years. Long time user.

All of the sudden it will not stay started.

It also states there is an update available, will go through the process until "done" but still keeps saying there is an update.

I am not super technical however I looked into the setting and don't see anything abnormal.

Please help. Thank you!

 

LOG:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-app-niceness.sh: executing...
[cont-init.d] 00-app-niceness.sh: exited 0.
[cont-init.d] 00-app-script.sh: executing...
[cont-init.d] 00-app-script.sh: exited 0.
[cont-init.d] 00-app-user-map.sh: executing...
[cont-init.d] 00-app-user-map.sh: exited 0.
[cont-init.d] 00-clean-logmonitor-states.sh: executing...
[cont-init.d] 00-clean-logmonitor-states.sh: exited 0.
[cont-init.d] 00-clean-tmp-dir.sh: executing...
[cont-init.d] 00-clean-tmp-dir.sh: exited 0.
[cont-init.d] 00-set-app-deps.sh: executing...
[cont-init.d] 00-set-app-deps.sh: exited 0.
[cont-init.d] 00-set-home.sh: executing...
[cont-init.d] 00-set-home.sh: exited 0.
[cont-init.d] 00-take-config-ownership.sh: executing...
[cont-init.d] 00-take-config-ownership.sh: exited 0.
[cont-init.d] 00-xdg-runtime-dir.sh: executing...
[cont-init.d] 00-xdg-runtime-dir.sh: exited 0.
[cont-init.d] 10-certs.sh: executing...
[cont-init.d] 10-certs.sh: exited 0.
[cont-init.d] 10-cjk-font.sh: executing...
[cont-init.d] 10-cjk-font.sh: exited 0.
[cont-init.d] 10-nginx.sh: executing...
[cont-init.d] 10-nginx.sh: exited 0.
[cont-init.d] 10-vnc-password.sh: executing...
[cont-init.d] 10-vnc-password.sh: exited 0.
[cont-init.d] 10-web-index.sh: executing...
[cont-init.d] 10-web-index.sh: exited 0.
[cont-init.d] crashplan-pro.sh: executing...
[cont-init.d] crashplan-pro.sh: setting CrashPlan Engine maximum memory to 8192M
sh: write error: No space left on device

[cont-init.d] crashplan-pro.sh: exited 1.
[services.d] stopping services
[services.d] stopping s6-fdholderd...
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-app-niceness.sh: executing...
[cont-init.d] 00-app-niceness.sh: exited 0.
[cont-init.d] 00-app-script.sh: executing...
[cont-init.d] 00-app-script.sh: exited 0.
[cont-init.d] 00-app-user-map.sh: executing...
[cont-init.d] 00-app-user-map.sh: exited 0.
[cont-init.d] 00-clean-logmonitor-states.sh: executing...
[cont-init.d] 00-clean-logmonitor-states.sh: exited 0.
[cont-init.d] 00-clean-tmp-dir.sh: executing...
[cont-init.d] 00-clean-tmp-dir.sh: exited 0.
[cont-init.d] 00-set-app-deps.sh: executing...
[cont-init.d] 00-set-app-deps.sh: exited 0.
[cont-init.d] 00-set-home.sh: executing...
[cont-init.d] 00-set-home.sh: exited 0.
[cont-init.d] 00-take-config-ownership.sh: executing...
[cont-init.d] 00-take-config-ownership.sh: exited 0.
[cont-init.d] 00-xdg-runtime-dir.sh: executing...
[cont-init.d] 00-xdg-runtime-dir.sh: exited 0.
[cont-init.d] 10-certs.sh: executing...
[cont-init.d] 10-certs.sh: exited 0.
[cont-init.d] 10-cjk-font.sh: executing...
[cont-init.d] 10-cjk-font.sh: exited 0.
[cont-init.d] 10-nginx.sh: executing...
[cont-init.d] 10-nginx.sh: exited 0.
[cont-init.d] 10-vnc-password.sh: executing...
[cont-init.d] 10-vnc-password.sh: exited 0.
[cont-init.d] 10-web-index.sh: executing...
[cont-init.d] 10-web-index.sh: exited 0.
[cont-init.d] crashplan-pro.sh: executing...
[cont-init.d] crashplan-pro.sh: setting CrashPlan Engine maximum memory to 8192M
sh: write error: No space left on device

[cont-init.d] crashplan-pro.sh: exited 1.
[services.d] stopping services
[services.d] stopping s6-fdholderd...
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
 

Link to post
On 10/23/2018 at 6:58 AM, Djoss said:

From your last screenshot, scroll down to see the "storage" folder.

I've spent over an hour trying to figure out why I couldn't locate the /storage folder as well. Exact same problem: just needed to scroll down. :$ The scroll bar was there, just not particularly visible for me I guess. Perhaps a slight UI adjustment is possible to make this more visible?

Link to post

Hi!

 

It seems Crashplan is active continuously, even at times when it is set not to run. This keeps the drives from spining down. Is there some setting that would allow the drives to spin down?

 

Thanks!

 

Karl

Link to post
  • 2 weeks later...

Anyone seeing "Waiting for Connection"?  I have gotten a couple alerts that server hasn't backed up in X days and I log in to check and it just says waiting for connection.  It will sometimes flash for a second over to preparing...or something but it's so quick I can't catch it all.  Says the last backup was 5.2 hours ago though so maybe working?

 

I flipped it from bridge to host just for kicks and there was no change.  Odd thing is flipping it back to bridge I am no longer to access the webui but if I leave it on host I can.  Still shows the waiting for connection.  Not sure if there is any issue with it being on host. 

Link to post

Mine has been working great for months but sometime in March it stopped connecting. I set up the 2 way authentication for the web login but something else must be messed up. I've looked through everything and it all seems good but in Unraid when you go to the WebUI and login it says "Unable to connect to destination for 10 days".  

 

Any ideas on where I should look?

 

I restarted the container and here is a log from where it started back up....maybe it has some useful info

 

[services.d] starting app...
[app] starting CrashPlan for Small Business...
07/04/2021 11:19:26 X DAMAGE available on display, using it for polling hints.
07/04/2021 11:19:26 To disable this behavior use: '-noxdamage'
07/04/2021 11:19:26
07/04/2021 11:19:26 Most compositing window managers like 'compiz' or 'beryl'
07/04/2021 11:19:26 cause X DAMAGE to fail, and so you may not see any screen
07/04/2021 11:19:26 updates via VNC. Either disable 'compiz' (recommended) or
07/04/2021 11:19:26 supply the x11vnc '-noxdamage' command line option.
07/04/2021 11:19:26 X COMPOSITE available on display, using it for window polling.
07/04/2021 11:19:26 To disable this behavior use: '-noxcomposite'
07/04/2021 11:19:26
07/04/2021 11:19:26 Wireframing: -wireframe mode is in effect for window moves.
07/04/2021 11:19:26 If this yields undesired behavior (poor response, painting
07/04/2021 11:19:26 errors, etc) it may be disabled:
07/04/2021 11:19:26 - use '-nowf' to disable wireframing completely.
07/04/2021 11:19:26 - use '-nowcr' to disable the Copy Rectangle after the
07/04/2021 11:19:26 moved window is released in the new position.
07/04/2021 11:19:26 Also see the -help entry for tuning parameters.
07/04/2021 11:19:26 You can press 3 Alt_L's (Left "Alt" key) in a row to
07/04/2021 11:19:26 repaint the screen, also see the -fixscreen option for
07/04/2021 11:19:26 periodic repaints.
07/04/2021 11:19:26 GrabServer control via XTEST.
[services.d] done.
07/04/2021 11:19:26
07/04/2021 11:19:26 Scroll Detection: -scrollcopyrect mode is in effect to
07/04/2021 11:19:26 use RECORD extension to try to detect scrolling windows
07/04/2021 11:19:26 (induced by either user keystroke or mouse input).
07/04/2021 11:19:26 If this yields undesired behavior (poor response, painting
07/04/2021 11:19:26 errors, etc) it may be disabled via: '-noscr'
07/04/2021 11:19:26 Also see the -help entry for tuning parameters.
07/04/2021 11:19:26 You can press 3 Alt_L's (Left "Alt" key) in a row to
07/04/2021 11:19:26 repaint the screen, also see the -fixscreen option for
07/04/2021 11:19:26 periodic repaints.
07/04/2021 11:19:26
07/04/2021 11:19:26 XKEYBOARD: number of keysyms per keycode 7 is greater
07/04/2021 11:19:26 than 4 and 51 keysyms are mapped above 4.
07/04/2021 11:19:26 Automatically switching to -xkb mode.
07/04/2021 11:19:26 If this makes the key mapping worse you can
07/04/2021 11:19:26 disable it with the "-noxkb" option.
07/04/2021 11:19:26 Also, remember "-remap DEAD" for accenting characters.
07/04/2021 11:19:26
07/04/2021 11:19:26 X FBPM extension not supported.
07/04/2021 11:19:26 X display is not capable of DPMS.
07/04/2021 11:19:26 --------------------------------------------------------
07/04/2021 11:19:26
07/04/2021 11:19:26 Default visual ID: 0x21
07/04/2021 11:19:26 Read initial data from X display into framebuffer.
07/04/2021 11:19:26 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/5120
07/04/2021 11:19:26
07/04/2021 11:19:26 X display :0 is 32bpp depth=24 true color
07/04/2021 11:19:26
07/04/2021 11:19:26 Listening for VNC connections on TCP port 5900
07/04/2021 11:19:26
07/04/2021 11:19:26 Xinerama is present and active (e.g. multi-head).
07/04/2021 11:19:26 Xinerama: number of sub-screens: 1
07/04/2021 11:19:26 Xinerama: no blackouts needed (only one sub-screen)
07/04/2021 11:19:26
07/04/2021 11:19:26 fb read rate: 861 MB/sec
07/04/2021 11:19:26 fast read: reset -wait ms to: 10
07/04/2021 11:19:26 fast read: reset -defer ms to: 10
07/04/2021 11:19:26 The X server says there are 10 mouse buttons.
07/04/2021 11:19:26 screen setup finished.
07/04/2021 11:19:26

The VNC desktop is: bceeb4c88123:0

0

******************************************************************************
Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?

The scheme stores pixel data offscreen on the VNC viewer side for faster
retrieval. It should work with any VNC viewer. Try it by running:

x11vnc -ncache 10 ...

One can also add -ncache_cr for smooth 'copyrect' window motion.
More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching

07/04/2021 11:20:04 Got connection from client 127.0.0.1
07/04/2021 11:20:04 other clients:
07/04/2021 11:20:04 Got 'ws' WebSockets handshake
07/04/2021 11:20:04 Got protocol: binary
07/04/2021 11:20:04 - webSocketsHandshake: using binary/raw encoding
07/04/2021 11:20:04 - WebSockets client version hybi-13
07/04/2021 11:20:04 Disabled X server key autorepeat.
07/04/2021 11:20:04 to force back on run: 'xset r on' (3 times)
07/04/2021 11:20:04 incr accepted_client=1 for 127.0.0.1:45350 sock=10
07/04/2021 11:20:04 Client Protocol Version 3.8
07/04/2021 11:20:04 Protocol version sent 3.8, using 3.8
07/04/2021 11:20:04 rfbProcessClientSecurityType: executing handler for type 1
07/04/2021 11:20:04 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
07/04/2021 11:20:04 Pixel format for client 127.0.0.1:
07/04/2021 11:20:04 32 bpp, depth 24, little endian
07/04/2021 11:20:04 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
07/04/2021 11:20:04 no translation needed
07/04/2021 11:20:04 Enabling NewFBSize protocol extension for client 127.0.0.1
07/04/2021 11:20:04 Enabling full-color cursor updates for client 127.0.0.1
07/04/2021 11:20:04 Using image quality level 6 for client 127.0.0.1
07/04/2021 11:20:04 Using JPEG subsampling 0, Q79 for client 127.0.0.1
07/04/2021 11:20:04 Using compression level 9 for client 127.0.0.1
07/04/2021 11:20:04 Enabling LastRect protocol extension for client 127.0.0.1
07/04/2021 11:20:04 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFECC)
07/04/2021 11:20:04 Using tight encoding for client 127.0.0.1
07/04/2021 11:20:05 client_set_net: 127.0.0.1 0.0000
07/04/2021 11:20:05 created xdamage object: 0x40002c
07/04/2021 11:20:05 copy_tiles: allocating first_line at size 41
07/04/2021 11:20:05 client_set_net: 127.0.0.1 0.0000
07/04/2021 11:20:05 created xdamage object: 0x40002c
07/04/2021 11:20:05 copy_tiles: allocating first_line at size 41
07/04/2021 11:20:14 created selwin: 0x40002d
07/04/2021 11:20:14 called initialize_xfixes()
07/04/2021 11:20:14 created selwin: 0x40002d
07/04/2021 11:20:14 called initialize_xfixes()
07/04/2021 11:20:14 client 1 network rate 523.3 KB/sec (18317.5 eff KB/sec)
07/04/2021 11:20:14 client 1 latency: 1.8 ms
07/04/2021 11:20:14 dt1: 0.0061, dt2: 0.0244 dt3: 0.0018 bytes: 15462
07/04/2021 11:20:14 link_rate: LR_LAN - 1 ms, 523 KB/s

07/04/2021 11:23:19 got closure, reason 1001
07/04/2021 11:23:19 rfbProcessClientNormalMessage: read: Connection reset by peer
07/04/2021 11:23:19 client_count: 0
07/04/2021 11:23:19 Restored X server key autorepeat to: 1
07/04/2021 11:23:19 Client 127.0.0.1 gone
07/04/2021 11:23:19 Statistics events Transmit/ RawEquiv ( saved)
07/04/2021 11:23:19 ServerCutText : 1 | 8/ 8 ( 0.0%)
07/04/2021 11:23:19 FramebufferUpdate : 234 | 0/ 0 ( 0.0%)
07/04/2021 11:23:19 LastRect : 21 | 252/ 252 ( 0.0%)
07/04/2021 11:23:19 tight : 430 | 313154/ 8603816 ( 96.4%)
07/04/2021 11:23:19 RichCursor : 1 | 1374/ 1374 ( 0.0%)
07/04/2021 11:23:19 TOTALS : 687 | 314788/ 8605450 ( 96.3%)
07/04/2021 11:23:19 Statistics events Received/ RawEquiv ( saved)
07/04/2021 11:23:19 KeyEvent : 30 | 240/ 240 ( 0.0%)
07/04/2021 11:23:19 PointerEvent : 92 | 552/ 552 ( 0.0%)
07/04/2021 11:23:19 FramebufferUpdate : 235 | 2350/ 2350 ( 0.0%)
07/04/2021 11:23:19 SetEncodings : 1 | 56/ 56 ( 0.0%)
07/04/2021 11:23:19 SetPixelFormat : 1 | 20/ 20 ( 0.0%)
07/04/2021 11:23:19 TOTALS : 359 | 3218/ 3218 ( 0.0%)
07/04/2021 11:23:19 destroyed xdamage object: 0x40002c
07/04/2021 11:23:19 Got connection from client 127.0.0.1
07/04/2021 11:23:19 other clients:
07/04/2021 11:23:19 Got 'ws' WebSockets handshake
07/04/2021 11:23:19 Got protocol: binary
07/04/2021 11:23:19 - webSocketsHandshake: using binary/raw encoding
07/04/2021 11:23:19 - WebSockets client version hybi-13
07/04/2021 11:23:19 Disabled X server key autorepeat.
07/04/2021 11:23:19 to force back on run: 'xset r on' (3 times)
07/04/2021 11:23:19 incr accepted_client=2 for 127.0.0.1:49534 sock=10
07/04/2021 11:23:19 Client Protocol Version 3.8
07/04/2021 11:23:19 Protocol version sent 3.8, using 3.8
07/04/2021 11:23:19 rfbProcessClientSecurityType: executing handler for type 1
07/04/2021 11:23:19 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
07/04/2021 11:23:19 Pixel format for client 127.0.0.1:
07/04/2021 11:23:19 32 bpp, depth 24, little endian
07/04/2021 11:23:19 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
07/04/2021 11:23:19 no translation needed
07/04/2021 11:23:19 Enabling NewFBSize protocol extension for client 127.0.0.1
07/04/2021 11:23:19 Enabling full-color cursor updates for client 127.0.0.1
07/04/2021 11:23:19 Using image quality level 6 for client 127.0.0.1
07/04/2021 11:23:19 Using JPEG subsampling 0, Q79 for client 127.0.0.1
07/04/2021 11:23:19 Using compression level 9 for client 127.0.0.1
07/04/2021 11:23:19 Enabling LastRect protocol extension for client 127.0.0.1
07/04/2021 11:23:19 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFECC)
07/04/2021 11:23:19 Using tight encoding for client 127.0.0.1
07/04/2021 11:23:19 client_set_net: 127.0.0.1 0.0000
07/04/2021 11:23:19 created xdamage object: 0x40002e
07/04/2021 11:23:24 client 2 network rate 663.8 KB/sec (17817.9 eff KB/sec)
07/04/2021 11:23:24 client 2 latency: 2.4 ms
07/04/2021 11:23:24 dt1: 0.0115, dt2: 0.0210 dt3: 0.0024 bytes: 20780
07/04/2021 11:23:24 link_rate: LR_LAN - 2 ms, 663 KB/s

Edited by SPOautos
Link to post

unable to connect for 15 days as well. I turned on 2step when Crashplan notified it as a requirement, but backups within unraid container continued to work until 15 days ago.  

Link to post
19 minutes ago, Djoss said:

Which error do you have exactly?  "waiting for connection" or "Unable to connect to destination" ?

waiting for connection - I did clear my cache and it started doing the sync file information so that is a good sign I think.  Will keep an eye on it once it finishes

Link to post
2 hours ago, Djoss said:

Which error do you have exactly?  "waiting for connection" or "Unable to connect to destination" ?

 I have unable to connect like SPOautos posted.

 

thank you

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.